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

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Thu, 12 March 2020 11:04 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 CB0AB3A0D38 for <v6ops@ietfa.amsl.com>; Thu, 12 Mar 2020 04:04:49 -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 zm8Bb9gi80uA for <v6ops@ietfa.amsl.com>; Thu, 12 Mar 2020 04:04:48 -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 0EEE43A0CE7 for <v6ops@ietf.org>; Thu, 12 Mar 2020 04:04:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1584011085; x=1584615885; 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=XU758j8z 5qeYH4JWs+OtsImaVkKMs8oN2APkPZjatSQ=; b=rIH8Pkm5lDcI46nUibYiIPkh E3UD3u/izorf3r2k5JVCZNPZMyFnb4gmqcTrXAk6LfSsEBJMDi210PMDMljtKqkr yjMX7+2VXxg1PYOUO5V0l85gqFHX9LkIqAff+V1tDr6X9caxktC+HnQI1rRtX4PF UpA59B6M7uHSg93RQN0=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Thu, 12 Mar 2020 12:04:45 +0100
X-Spam-Processed: mail.consulintel.es, Thu, 12 Mar 2020 12:04:45 +0100
Received: from [10.10.10.144] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50000089019.msg for <v6ops@ietf.org>; Thu, 12 Mar 2020 12:04:45 +0100
X-MDRemoteIP: 2001:470:1f09:495:e0a6:81ab:ea8d:1a06
X-MDHelo: [10.10.10.144]
X-MDArrival-Date: Thu, 12 Mar 2020 12:04:45 +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 12:04:44 +0100
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: v6ops@ietf.org
Message-ID: <1C8D1394-B226-4727-9E01-853A6CEA35AF@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> <1FC68A89-A5E2-4FF3-836C-5AEC3D295299@delong.com>
In-Reply-To: <1FC68A89-A5E2-4FF3-836C-5AEC3D295299@delong.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/X9mP0JngaM5bNfo6YP8PVA1TEO0>
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 11:04:57 -0000

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

[Jordi] I think we agree in that, if at the same time we don't exclude that this scenario may have (end-to-end) some form of IPv4-transport or tunnel on top of IPv6, unless it is specifically "filtered" or "avoided" by the network (obvious security reasons).

So, in those cases, I think it should be stated as well, to make it clear.

Is the same as if you have a lot of security filtering in the firewall, but you allow an employee to setup a VPN ...

I think I could include something about that in the next version, to make it clear.







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