IETF Logo Mail Archive

Re: IPv6 only host NAT64 requirements?

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 20 November 2017 23:44 UTC

Return-Path: <brian.e.carpenter@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 0E1F3129AA8 for <ipv6@ietfa.amsl.com>; Mon, 20 Nov 2017 15:44:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_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 2XGbjz4rIAev for <ipv6@ietfa.amsl.com>; Mon, 20 Nov 2017 15:44:55 -0800 (PST)
Received: from mail-pf0-x235.google.com (mail-pf0-x235.google.com [IPv6:2607:f8b0:400e:c00::235]) (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 F19F5120713 for <ipv6@ietf.org>; Mon, 20 Nov 2017 15:44:54 -0800 (PST)
Received: by mail-pf0-x235.google.com with SMTP id q4so8446820pfg.13 for <ipv6@ietf.org>; Mon, 20 Nov 2017 15:44:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Y2yDQnP+5Mbl/psXQvq97NSELXNDc5uEpbcfeOmlnjE=; b=gF0PyKdh4Q9sPWauFjv479NwrGPCIKWE6s1l9PQOQiiEMLQRXZ3bG3ftQT0iirE8fa +PUGwz8XRMtZyPmWThpGYJhu5DhEGpjyPS7L7hY7dYC1oTmlWFMa9cKp4+Lg8Ky9SNMR kq1tGlDCm4ph/n+Q6vqKTXV+nYamBDIZ+K3NxFGbBcYgFRhvLFc/7svPfONRR2/G2l4G 77JCOPGCBE1FBc6CJz0QFsL2UghHbP5jPSMXHwK+O8Y2boFm2bB0YX0uJq/TYPv+woJf du/dfBybb/HPT1umhEPc2pKMFGQ20C96IU+ICa07wr874b0RF/OUvdLEHj3Ah3syaPu7 d/Jg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=Y2yDQnP+5Mbl/psXQvq97NSELXNDc5uEpbcfeOmlnjE=; b=Si8+i6s4dWhKsCjm4BvPT1KLdyhfgq4lgdxa/JjtZ0O3Zl+l5g16MQkFnAT6pMci5L zOXCQNm196IQo9asku/jhxsVflpoIQJGKmfhXP8tnStaZVGcV3Ue3j7jO7eMRRPI4/e3 gCslt0xA4NM5GKlqfYmNZiQI3208CcsTgFaYUIjGCJTfMXBKXco22ek+4YdIlp/fxO7F rjJvh5zWBj6pGE/KMCm9jIz6dF8KzJOLnQGKFQcehP2oZtY0qbU7ooI5ImpcYHVCmvxB 7CHFGOJKVW6881ZirTWjqYWWe5kFlGIjZrPZQGN80WPGtPvT42A4iEL4UcmaF0qmhSpG DN2g==
X-Gm-Message-State: AJaThX56AGsSWTZucFXLGLcIxrpe92O8QocJcgg78SvS5ehc8ocmF5eH jhB2gIxgt5Enbdh7xphGMsh2XA==
X-Google-Smtp-Source: AGs4zMbj5Hes0jaYp8IggmyLhPW3yIqT+eOpu8V8P1Q10pNL34wdLGtq4I51InRDhtH3wuTCgqvReg==
X-Received: by 10.98.159.135 with SMTP id v7mr822401pfk.162.1511221494129; Mon, 20 Nov 2017 15:44:54 -0800 (PST)
Received: from [130.216.38.102] (sc-cs-567-laptop.uoa.auckland.ac.nz. [130.216.38.102]) by smtp.gmail.com with ESMTPSA id n72sm22724097pfg.109.2017.11.20.15.44.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 20 Nov 2017 15:44:53 -0800 (PST)
Subject: Re: IPv6 only host NAT64 requirements?
To: Jen Linkova <furry13@gmail.com>, "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Cc: 6man WG <ipv6@ietf.org>
References: <m1eEGbJ-0000EhC@stereo.hq.phicoh.net> <787AE7BB302AE849A7480A190F8B93300A07AD68@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CAFU7BARoXgodiTJfTGc1dUfQ8-ER_r8UOE1c3h-+G0KTeCgBew@mail.gmail.com> <787AE7BB302AE849A7480A190F8B93300A07C625@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <7EE41034-132E-45F0-8F76-6BA6AFE3E916@employees.org> <787AE7BB302AE849A7480A190F8B93300A07D481@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <0C83562D-859B-438C-9A90-2480BB166737@employees.org> <787AE7BB302AE849A7480A190F8B93300A07D534@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <26A31D20-46C2-473E-9565-59E5BA85ED8B@employees.org> <787AE7BB302AE849A7480A190F8B93300A07D63D@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <F9E3BD88-38E0-4329-A4BF-22083A023268@employees.org> <f673d6c7-570e-b2b8-e8aa-15d73ea8ba3f@gmail.com> <e697e64116f245f0b462a1a2277c704b@XCH15-06-11.nw.nos.boeing.com> <CAFU7BARe88myZsmbe-ssJ=M3aYCTz-et7wA7dxKA-X9DEbD8Dg@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <2b0b213c-2ef5-a1cf-4f6e-92e4e6841baa@gmail.com>
Date: Tue, 21 Nov 2017 12:44:52 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <CAFU7BARe88myZsmbe-ssJ=M3aYCTz-et7wA7dxKA-X9DEbD8Dg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/N62r0iGPAV2c53eOL51MNwbYx18>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 20 Nov 2017 23:44:56 -0000

Jen,
On 21/11/2017 09:33, Jen Linkova wrote:
> On Tue, Nov 21, 2017 at 7:12 AM, Manfredi, Albert E
> <albert.e.manfredi@boeing.com> wrote:
>> Very instructive thread for me, I must say. I'm getting this sense of urgency, to be rid of IPv4, but it comes from the IETF 6man wg and some ISPs.
>> Ultimately, it's not up to 6man to decide.
> 
> I do not see this thread as 6man deciding that everyone is to get rid
> of Ipv4 right now. I see it as 'there are networks deploying IPv6-only
> hosts and 6man is discussing how to help hosts to operate in such
> environment'.

Fair enough. But now, and for many years, IPv6-only hosts** will
be unusual (except on some cellular networks); IPv4-only hosts are 
common, and dual stack hosts are common.

** In my book, a host that contains even one IPv4-only application
cannot be considered as an "IPv6-only" host.
 
>> It's up to device vendors,  and up to the deployed base of devices.
>> The IETF can only suggest, and ISP networks have to meet the real world needs.
> 
> People from the real world is coming to IETF saying 'we are deploying
> Ipv6-only hosts' [1] [2]

Sure. And I think the tests last week showed two things:
1. NAT64/DNS64 is viable for IPv6-only hosts (setting aside DNSSEC).
2. IPv6-only hosts are far from universal, even among IETF
participants.

And BTW thanks for the effort behind ietf-nat64. I think it
was a very valuable effort.

Regards,
    Brian

v2.23.0 | Report a Bug | By Email