Re: [v6ops] About Req for Comments - "Transition to IPv6"

Fred Baker <fredbaker.ietf@gmail.com> Thu, 12 March 2020 02:06 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 EA5C53A1138 for <v6ops@ietfa.amsl.com>; Wed, 11 Mar 2020 19:06:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, 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 tB9ZBh-VWxFl for <v6ops@ietfa.amsl.com>; Wed, 11 Mar 2020 19:06:48 -0700 (PDT)
Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) (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 B6A8C3A1135 for <v6ops@ietf.org>; Wed, 11 Mar 2020 19:06:47 -0700 (PDT)
Received: by mail-wr1-x436.google.com with SMTP id s14so5364236wrt.8 for <v6ops@ietf.org>; Wed, 11 Mar 2020 19:06:47 -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=lQcL4zeqxL7WwcZ4KMbE+VJlva/lg8h1Bv3IHEzU1hM=; b=svFokEBlfyohqtpt+xA3qstCglUXyjNGlVyGqOvbsLQidPhkVHKs9aJ0F/pW92lolR Dmtj8SlM9nXARb4e5KN26cEHxSffV7AaBP5GF5Pb8uTGsbB2LaNNirk9lI+p9h4LsjnS B8rF6LXDIlL03sBwSydkCD4wcmY4sts06KVIfSkXPcwT/36j02z9qjqFyUbNQs2X0i94 TwwOZgZmKi4BJFEvO9PGhDUMCguagS5KXJO2oeDdN5pZlkGsj0RdXS9hB4h51alXYNUv YJ5Ww6G2ggl6jARKkNO3HxIG5nkmk8o4jgKPs0ZrYYNg/KVe6Bi08D09/mx9WPsYz93O 5cPw==
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=lQcL4zeqxL7WwcZ4KMbE+VJlva/lg8h1Bv3IHEzU1hM=; b=DJcoxDX70TLLEY4PNl2ghmjOJgCaSxSp52oqi0sTBJiod0WEkqbE+HH+dg+TfiweY5 nycWepvRmDPGrJvEt+T9PBn1szgPoS0lrCCNGIbHaguSN0am1mpSimxpZMyMGaCprvR7 vlxll/LzNB04JPpShz0VtCrbaU1on2TJkrurrDsC3sue6GGjArNuv9KT9mroFI/SyrvW vkm9NTHmlq32IPDq+jWnqLZtx5Z8M9q/0gvoZZ1mGfVFozc3ohBPC8ezOYdxwF7s30A/ spVpeSH27t5sblvB3RqpipUkgFqD1yADjcOmWvPHh2lRMO78pKADMRTNwnFbSuQAn6R0 n0dA==
X-Gm-Message-State: ANhLgQ3vj5RtyUb/8Nbm9zEDH4hthJh48cETR2P6NGTmAuKQP8Gnfkhm +Dgjzc0jJZXHeVueGAZgfrc=
X-Google-Smtp-Source: ADFU+vuwnL/dVImc1EkNc1qSUh1x/BjOkryBRqMCYz8+IWAP4fu84/8GbSbKDpsM4JaSfsFwnL9//g==
X-Received: by 2002:adf:eece:: with SMTP id a14mr7835198wrp.334.1583978806109; Wed, 11 Mar 2020 19:06:46 -0700 (PDT)
Received: from ?IPv6:2600:8802:5900:13c4::1041? ([2600:8802:5900:13c4::1041]) by smtp.gmail.com with ESMTPSA id m2sm10643757wml.24.2020.03.11.19.06.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 Mar 2020 19:06:44 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <3567F570-BC40-470E-971B-2368E1ACD80C@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_CD54D11C-7E34-4EE6-B5C0-1303E5E784DB"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Date: Wed, 11 Mar 2020 19:06:41 -0700
In-Reply-To: <43D0E5A1-E5C5-4ACA-A44D-BC2F67129174@delong.com>
Cc: Alexandre Petrescu <alexandre.petrescu@gmail.com>, v6ops@ietf.org
To: Owen DeLong <owen@delong.com>
References: <e8a25961-5ac9-d35e-77dd-bf86f45cd077@gmail.com> <7eb4dc25-28a6-4927-2356-846e200681d2@gmail.com> <0791D4B0-8390-48D7-AF0A-CE004EC3224C@consulintel.es> <ccc75efb-8c00-ee97-5cc7-2e061e6e5a54@gmail.com> <52b6b9a4f46a49598eccee1b35e5efc5@irs.gov> <89127c25-9c51-c4bb-97ae-3567e80a4c52@gmail.com> <43D0E5A1-E5C5-4ACA-A44D-BC2F67129174@delong.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/aNEBQKzGa-DsIw-ckTzAwjcvGxE>
Subject: Re: [v6ops] About Req for Comments - "Transition to IPv6"
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 12 Mar 2020 02:06:50 -0000


> On Mar 5, 2020, at 8:46 AM, Owen DeLong <owen@delong.com> wrote:
> 
>> Thank you very much for the pointer.  In it I could spot
>> the following footnote: "[4] IPv6-Only refers to network environments in
>> which use of the IPv4 protocol has been eliminated.”
> 
> IPv6-Only refers to network environments which are not using IPv4. That could be a network where IPv4 has been eliminated (rare at this time, though Facebook is a significant example) or it could be a greenfield deployment where IPv4 was never deployed.

<sans hats>

This, I think, is where the v6ops discussion has travelled in circles forever. To me, I would drop the word "network" and say that it is a specified environment. If I say that a system is IPv6-only, it is not using IPv6 internally or externally. It might or might not have IPv4 code in it, but it's not using it. If I say that a LAN, building, etc is IPv6-only, it is not to say that it couldn't have IPv4 in it if a DHCP server started handing out such addresses, but that it *doesn't*. If it is an Autonomous System, it means that only IPv6 is in use in that domain.

As soon as we get into the "but it could" or "was it translated from something else" or whatever rathole, we're into a discussion of angels, pins, and heads of pins. It will not end, because it can't. Someone will forever come up with a "what if" scenario to stir the pot.

Speaking for myself, I would have the user of the term identify the environment s/he is talking about, and say that *within*that*domain* communication is entirely accomplished using IPv6.

And STOP.