Re: [v6ops] Time to dump dual-stack networks and get on the IPv6 train - with LW4o6

Fred Baker <fredbaker.ietf@gmail.com> Mon, 02 July 2018 06:28 UTC

Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9048130E3F for <v6ops@ietfa.amsl.com>; Sun, 1 Jul 2018 23:28:37 -0700 (PDT)
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=unavailable 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 XLsww8o24p49 for <v6ops@ietfa.amsl.com>; Sun, 1 Jul 2018 23:28:32 -0700 (PDT)
Received: from mail-oi0-x233.google.com (mail-oi0-x233.google.com [IPv6:2607:f8b0:4003:c06::233]) (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 49FDC130F26 for <v6ops@ietf.org>; Sun, 1 Jul 2018 23:28:25 -0700 (PDT)
Received: by mail-oi0-x233.google.com with SMTP id i12-v6so9879612oik.2 for <v6ops@ietf.org>; Sun, 01 Jul 2018 23:28:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=gUYqyEE0mXSpEb1Ry5OZfo35YAqFpLuNoGvg2661qQU=; b=rsKr1EcgEscftbQBk62eF4HfHljoXoSqsyhIz712gc1OvNPURYyG9O5m6cmjlnJ5XI jnaPSeSFbAZjraU3KF6/BTKFZcaLRVY08zb9MweO1mxiwkpMALDgE+FU/mh2k0L36dzE de5MhQC1jAeCRqB9L/o0ig194lbHcpnW2Eu15kWSN1GN8vDjtoF0GKocFJvurshpPThC CmqLus8BU5PpfUi2FbhjQq4uqjzkAYZ6dNiw3aGqRRAhdwjSVegfODuDejhvCLh99UXn SLYF7rPfDUcSSq8BqsudfKTAeP+6Uc3bCVASC8rad+2EYY82Ftn3rNpuEQnrjcWhGfx4 BhSg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=gUYqyEE0mXSpEb1Ry5OZfo35YAqFpLuNoGvg2661qQU=; b=if1+bMDdwf+VQ0cUrvAKV2TLtCxsZ0KFphNC6U7V+N2nrdxmM9a/bvtm5j2+5tedvQ Pgi4mJSeTRw6/9VS83AZClRZiLVABfazRAsjLFgpP8G2infc48WYWu1zn5CQh+hvGc0g JBv5t64HdnDGa840MGQXCS/UuAd9XOmgRhhXtQA0ouxUhjG/qfCcFiQOLk/+oCy6neB9 QofZYKzLN4o4gwwchKVJCQ0TAokKWTmERqL3buj4i0cBtFMDqk1DaMtmIUnq+UzC36zk NTRzxfHMH90yc9/eanycI+aMWFNyAHPbme4o090Sp/Oac5/jVXIrw58c96XrGKgMNEU6 8PtQ==
X-Gm-Message-State: APt69E04W1vrZ7AdYYjc7EUHFsxRGwxTF4NC30RPvcDJ4OcByAM/tx2n vNTohIpVEt6Xi6L8yOVZQlTsJTdP
X-Google-Smtp-Source: AAOMgpf9ttnZDnMO0dOpJujy7IkbAi+1CU1RWmDtfDW+UVi4EzJ7zzuypfOrByAvwCyhNrAF/8YS3Q==
X-Received: by 2002:aca:41d6:: with SMTP id o205-v6mr14918317oia.38.1530512904704; Sun, 01 Jul 2018 23:28:24 -0700 (PDT)
Received: from ?IPv6:2600:8802:5600:1546::101b? ([2600:8802:5600:1546::101b]) by smtp.gmail.com with ESMTPSA id k189-v6sm7382119oif.32.2018.07.01.23.28.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 01 Jul 2018 23:28:23 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <6E48293C-17F9-4376-9E2A-B87903093953@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_ED72267A-4BD7-4A8A-A0DE-CDB01A381846"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Sun, 01 Jul 2018 23:28:22 -0700
In-Reply-To: <CAKr6gn2W8wh5ogbgnZXLw4zOY6M6tGGF+aZK1Tq75wTs9HCm=g@mail.gmail.com>
Cc: Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>, "v6ops@ietf.org WG" <v6ops@ietf.org>
To: George Michaelson <ggm@algebras.org>
References: <057742AA-226E-44F8-819E-C865D7F58758@gmail.com> <c29a04f9-488d-62a9-29c6-35fce8920edd@gmail.com> <CAKD1Yr3cu-V7gVMxcVL1hXgvkJPX2N+bC9QJq+fcApyLOPyeWQ@mail.gmail.com> <CAKr6gn2W8wh5ogbgnZXLw4zOY6M6tGGF+aZK1Tq75wTs9HCm=g@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/yhz_5z7WbBa9SAnUjIstqvEW4lM>
Subject: Re: [v6ops] Time to dump dual-stack networks and get on the IPv6 train - with LW4o6
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jul 2018 06:28:38 -0000

On Jul 1, 2018, at 7:53 PM, George Michaelson <ggm@algebras.org> wrote:
> I know its "wrong" but I sympathise with a tech journalist seeking
> clarity in this. The edge user situation is very hard to distinguish
> in both cases, the user functionally can see both Ipv4 and Ipv6
> resources. How is this not "dual" in the sense a man or woman in the
> street would understand it?

Of course. From the perspective of a residential - or enterprise - user, they have both IPv4 and IPv6, and the network is carrying them. So from their perspective they retain dual stack capabilities in the near term. However, here's another factoid.

For the residential user, the number of services that actually require IPv4 is relatively small. I mentioned home security as a market that required the ability to make an IPv4 connection to the home. Suppose that could be changed? One way to change that would be for a few large ISPs to convince companies like LINK or ADT to become IPv6-capable, whereupon it becomes a market requirement for their competitors.

The ISP has just made having IPv4 at all a second priority for them; it's in their interest to move residential/soho/enterprise to IPv6, with the goal of removing the final translation step. I would expect their next move to be to charge for the service, and if possible move it to the edge itself  - which is where draft-*-v6ops-nat64-deployment is going. The transition rolls out from there.

The more outfits that find it in their interest to be able to operate without IPv4 at all, the better this is for all of us. And this becomes an important step in the general transition.