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

Owen DeLong <owen@delong.com> Sun, 15 March 2020 17:48 UTC

Return-Path: <owen@delong.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 3E8B33A19AF for <v6ops@ietfa.amsl.com>; Sun, 15 Mar 2020 10:48:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.099
X-Spam-Level:
X-Spam-Status: No, score=-1.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 FgseXgbDKnbN for <v6ops@ietfa.amsl.com>; Sun, 15 Mar 2020 10:48:15 -0700 (PDT)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id BE1093A19AD for <v6ops@ietf.org>; Sun, 15 Mar 2020 10:48:15 -0700 (PDT)
Received: from kiev.delong.com (kiev.delong.com [IPv6:2620:0:930:0:0:0:200:5]) (authenticated bits=0) by owen.delong.com (8.15.2/8.15.2) with ESMTPSA id 02FHmCuK3861741 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 15 Mar 2020 10:48:13 -0700
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Owen DeLong <owen@delong.com>
In-Reply-To: <75DB7A3D-74D6-477B-A6C1-57638C070576@gmail.com>
Date: Sun, 15 Mar 2020 10:48:12 -0700
Cc: JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org>, v6ops@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <DBBB31A0-23F3-4038-82BF-738B49F183B3@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> <3567F570-BC40-470E-971B-2368E1ACD80C@gmail.com> <1FC68A89-A5E2-4FF3-836C-5AEC3D295299@delong.com> <C83F2033-C11C-4664-9242-2500737F7E5D@consulintel.es> <B58EAE26-53FE-476B-BC40-9EFF2CF7D06A@consulintel.es> <75DB7A3D-74D6-477B-A6C1-57638C070576@gmail.com>
To: Fred Baker <fredbaker.ietf@gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (owen.delong.com [IPv6:2620:0:930:0:0:0:200:2]); Sun, 15 Mar 2020 10:48:13 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/BvNzQUuW0VGoa3kTWuodVo36PG8>
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: Sun, 15 Mar 2020 17:48:18 -0000


> On Mar 15, 2020, at 10:30 , Fred Baker <fredbaker.ietf@gmail.com> wrote:
> 
> 
> 
>> On Mar 12, 2020, at 4:17 AM, JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org> wrote:
>> 
>> 12.  IPv4 Exclusion
>> 
>>  If an IPv6-only network or part of it, has strict filtering rules to
>>  avoid IPv4 to be transported on top of IPv6, this should be
>>  explicitly cited.  For example, and enterprise LAN, where employees
>>  can't use VPNs, tunnels, or even translations, could be named as
>>  "IPv6-only LAN with IPv4 Exclusion".
>> 
>> El 12/3/20 12:04, "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es> escribió:
>> 
>>       	+	Any environment where IPv4 usage has been discontinued and IPv6 is the sole remaining active protocol
>>       OR
>>       	+	Any environment where IPv4 was never deployed and IPv6 is the only protocol ever deployed
>> 
>>       It was in response to a statement that IPv6-only could only mean an environment where IPv4 once existed and had been removed.
> 
> Sigh. You have heard me say this before, and I'll say it again. This is me saying it now.
> 
> "I'm sure we can make this complicated if we try hard enough."
> 
> To me, and yes, Owen, I'm agreeing with you, an IPv6-only *anything* is a thing that is only using IPv6. If the character string "IPv4" shows up somewhere in the definition, it is overly complex. If you want to discuss an IPv6-only puppy kennel, there are two things that should show up in the dentition: that it is a puppy kennel, and that it only uses IPv6 to communicate.

Fair enough, and I somewhat agree with you, but even that statement runs into problems if one gets pedantic. IPv6 only surely isn’t intended to exclude, e.g. UNIX domain sockets, named pipes, etc.

In fact, is it even our intent that “IPv6-only” should preclude the use of other non-IP networking protocols?

Perhaps: IPv6-only means a system or environment where the only version of Internet Protocol in use is Version 6.

Does that work?

Owen