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

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Thu, 12 March 2020 10:33 UTC

Return-Path: <prvs=1340af7d02=jordi.palet@consulintel.es>
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 001A83A09CD for <v6ops@ietfa.amsl.com>; Thu, 12 Mar 2020 03:33:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es
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 QFDXCqkgsoZU for <v6ops@ietfa.amsl.com>; Thu, 12 Mar 2020 03:33:18 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7869A3A09D2 for <v6ops@ietf.org>; Thu, 12 Mar 2020 03:33:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1584009195; x=1584613995; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:Message-ID:Thread-Topic:References:In-Reply-To: Mime-version:Content-type:Content-transfer-encoding; bh=qU0YxIRa MRNEQ7VRXfTFVlRPU9cIqVRQxUwlxatEw7Y=; b=s36gBBWOJ9Cyl4IxKOpbad3O 628q1wfVYdWrR7hkaERhaKbb1Q1x8xIALWVdMSICd1JMS6tS+1Hhfi1KP5P3AUtP ORxMwLS1ffw61I6lcakNHqjQb0sMppFLU44YydvmtOeS6c18k4MUHQrKoOHTZc2P DuY2Fa+USLVjSVzOS7s=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Thu, 12 Mar 2020 11:33:15 +0100
X-Spam-Processed: mail.consulintel.es, Thu, 12 Mar 2020 11:33:15 +0100
Received: from [10.10.10.144] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50000088993.msg for <v6ops@ietf.org>; Thu, 12 Mar 2020 11:33:14 +0100
X-MDRemoteIP: 2001:470:1f09:495:e0a6:81ab:ea8d:1a06
X-MDHelo: [10.10.10.144]
X-MDArrival-Date: Thu, 12 Mar 2020 11:33:14 +0100
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1340af7d02=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
User-Agent: Microsoft-MacOutlook/16.35.20030802
Date: Thu, 12 Mar 2020 11:33:11 +0100
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: v6ops@ietf.org
Message-ID: <D85E39E1-3E56-4353-9A14-159CF0775AE2@consulintel.es>
Thread-Topic: [v6ops] About Req for Comments - "Transition to IPv6"
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>
In-Reply-To: <3567F570-BC40-470E-971B-2368E1ACD80C@gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/MfQVTR4UyORDcWBLIep14qpvTwE>
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 10:33:20 -0000

Hi Fred,

In my document, instead of network, I try to explain that "what part of the network" should be explicited.

If you use IPv6-only network, then we mean "the complete network".

If you want to say in the WAN/access network, this is clear as well.

I think using scenario will present the same problem. If we call scenario a given network, we are talking about the full network. If we say WAN-scenario, is the same as WAN-network, we are just expliciting that is not the full network, but only that specific part.

I know that you are talking here about the OMB document, but I will like to understad if you think (hat-off) the way the document try to work on this terminology is good enough, or you suggest any changes.

Thanks!


El 12/3/20 3:07, "v6ops en nombre de Fred Baker" <v6ops-bounces@ietf.org en nombre de fredbaker.ietf@gmail.com> escribió:

    
    
    > 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.
    _______________________________________________
    v6ops mailing list
    v6ops@ietf.org
    https://www.ietf.org/mailman/listinfo/v6ops
    



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.