Re: IPv6 only host NAT64 requirements?

Jen Linkova <furry13@gmail.com> Mon, 20 November 2017 20:34 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 3169712E041 for <ipv6@ietfa.amsl.com>; Mon, 20 Nov 2017 12:34:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 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_LOW=-0.7, 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 StRzc54lTaog for <ipv6@ietfa.amsl.com>; Mon, 20 Nov 2017 12:34:14 -0800 (PST)
Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::229]) (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 DEFE6120713 for <ipv6@ietf.org>; Mon, 20 Nov 2017 12:34:13 -0800 (PST)
Received: by mail-lf0-x229.google.com with SMTP id x68so11593615lff.0 for <ipv6@ietf.org>; Mon, 20 Nov 2017 12:34:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=zu+bIKdfgeKFwwYm5C40Dp/H0ahEsssK0aghAh5Cp8I=; b=uTsjBcGqFzOqjPWgGqvTv1YPbQnquaEXJSRYxhgbCsjy6+u53HzPBGAsP4OKB+r/y2 FwXig7ltLC0pUguUcdtA4AOFdq/yjcmqAX5p4o0GbhGcCInGPg+F6KBxZch+WnkKwM0M mcfcvX3SZy1JcgJxNeThuiJcF2End7ZHR5x/1qhNc5rHgnvEwkas2gJ2XXQbYtYMLpSf U5fYqg7l1O4wswx25Loc1qlCAYaUCle3ucaH4KFUWc20NLa9FOx7jBbyOorWDH5zjAGG 4hKfbUI0OUb9hQyCTGbujNq/CZE8fNQ/zSnl+zx10k01e9CKw8iOYDyXVmyxFHImcMQZ Iepg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=zu+bIKdfgeKFwwYm5C40Dp/H0ahEsssK0aghAh5Cp8I=; b=G9KZp9txmJIIAtZe2uUlJtotZ40Z+W58aNbvayVZVT9fEyBJoP0OpTsG8oprYVCY8G MwSgspk0BuJz2MxHpfSrbR/VzDsPU/qJkInTqOowwSIf0aXEKNIYt2bq00K6r9zAd7g/ +6zZZ4/RbcoF5Pz+5jS7wvMm7GAwDnO+DG6IKak9xj0rrLko1MgF60ihyT6p+ZmAneQI FzwZhFZ+71aLhIiQ2FQSQH4kbj1xETLHJxaLG4OJW4UPm1KvsVhWsMf6GcMyiEngXKXL Qp9FKLubfRaoWiVclhfTC0xKZwcEEqbOTYheKOiLgLHR4i4CTVlTzl9l4Fhc9Y2XeeBh oGpQ==
X-Gm-Message-State: AJaThX4ifdc/85tolHSpQT6nS3vy4MZmOj68nHFNqPNC0lgBR42SaQGk DbQ+Der/oqDLlZ6JxDv2oCBUTvwlcAC9QePRkIE=
X-Google-Smtp-Source: AGs4zMZeDOGOLQnGtKK+CrUFVPmHw8pk+GbyoQuQ8bYpw67nG3whZcaSg8FCEvtcS1duiPspEouMvggGQN6u2dzvMAA=
X-Received: by 10.25.26.4 with SMTP id a4mr2124513lfa.105.1511210051999; Mon, 20 Nov 2017 12:34:11 -0800 (PST)
MIME-Version: 1.0
Received: by 10.25.205.2 with HTTP; Mon, 20 Nov 2017 12:33:50 -0800 (PST)
In-Reply-To: <e697e64116f245f0b462a1a2277c704b@XCH15-06-11.nw.nos.boeing.com>
References: <m1eEGbJ-0000EhC@stereo.hq.phicoh.net> <44A862B7-7182-4B3A-B46E-73065FC4D852@isc.org> <D42D8D7A-6D19-4862-9BB3-4913058A83B6@employees.org> <CAFU7BARCLq9eznccEtkdnKPAtKNT7Mf1bW0uZByPvxtiSrv6EQ@mail.gmail.com> <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>
From: Jen Linkova <furry13@gmail.com>
Date: Tue, 21 Nov 2017 07:33:50 +1100
Message-ID: <CAFU7BARe88myZsmbe-ssJ=M3aYCTz-et7wA7dxKA-X9DEbD8Dg@mail.gmail.com>
Subject: Re: IPv6 only host NAT64 requirements?
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, 6man WG <ipv6@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/KaZ4w85c-g7hlTAud7Em6MQuOM0>
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 20:34:16 -0000

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

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

References:
[1[ https://datatracker.ietf.org/meeting/100/materials/slides-100-v6ops-sessa-ipv6-only-deployment-at-cisco/
[2] https://datatracker.ietf.org/meeting/99/materials/agenda-99-v6ops/

>> Dual stack in every hotel room in the world is viable, from the
>> hotel guests' point of view.
>
> This seems the most practical answer, whether it's a client server model, such as in a hotel room, or a peer to peer network. In a mostly peer to peer network, the normal case would be for IPv6 hosts to be introduced gradually. I'm not sure how anything other than dual stack can work, in this case. If the goal is to have continuous robust operation of the network, during an indefinitely long transitional phase, because no one up the chain could care less about the nitty gritty, they just want everything to keep working flawlessly, then what motivation would there be for anything other than dual stack? The only practical solution is to introduce IPv6 hosts only if they are dual stack. And then carefully, on a case by case basis, individual subsystems that do not need to interoperate with IPv4 subsystems can shut off IPv4.
>
> I realize that such transition drag on for years. But again, in the greater scheme of things, this matters very little to those who must make sure the systems work at all times.
>
> Bert
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------



-- 
SY, Jen Linkova aka Furry