[v6ops] IPREF as a transitioning tool
waldemar <waldemar@wdmsys.com> Wed, 08 November 2023 09:08 UTC
Return-Path: <waldemar@wdmsys.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 891BFC09B5E2 for <v6ops@ietfa.amsl.com>; Wed, 8 Nov 2023 01:08:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=wdmsys.com header.b="XNSfFQ3v"; dkim=pass (2048-bit key) header.d=outbound.mailhop.org header.b="f9kUfVAf"
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NF6aXCBdFoKj for <v6ops@ietfa.amsl.com>; Wed, 8 Nov 2023 01:08:44 -0800 (PST)
Received: from bee.elm.relay.mailchannels.net (bee.elm.relay.mailchannels.net [23.83.212.14]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20D10C1D2D6E for <v6ops@ietf.org>; Wed, 8 Nov 2023 01:08:21 -0800 (PST)
X-Sender-Id: _forwarded-from|168.235.72.19
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 3DCDC842661 for <v6ops@ietf.org>; Wed, 8 Nov 2023 09:08:21 +0000 (UTC)
Received: from outbound3d.ore.mailhop.org (unknown [127.0.0.6]) (Authenticated sender: duocircle) by relay.mailchannels.net (Postfix) with ESMTPA id EDA6284277D for <v6ops@ietf.org>; Wed, 8 Nov 2023 09:08:20 +0000 (UTC)
ARC-Seal: i=2; s=arc-2022; d=mailchannels.net; t=1699434500; a=rsa-sha256; cv=pass; b=FfkuE0BuYdX+knSigQb8fOmnllrXygitUuzJqyqmRvGWP3SJO8Obe3IuYZFHjwt02xtAXs Yqykr0j3vlaZfSqphSMUpDg7iE5xHn203jYS0q+lgnDNTqWjjfLTSgvkXZdgo7ZeWY7G2k fFHdAGh8J7OpsI7mLHg70zmTFJz9yDuBBDIeG4pA9H3vwVo36o8jlX2v+adn+vmo4uAT6j 0YRgkvWdS69mqvZooDwWONI8kf+bf7yiR4EaL0IP3HlSyC8v9HhPsJbDveWN1zAdqgPVag uh8LXvMu0u/6hnIQFGHW/M5DhQn9PDzcWm1nnE9g78f010mq8QQPjxhy6E8VaQ==
ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=mailchannels.net; s=arc-2022; t=1699434500; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding:dkim-signature; bh=PC7twUx1UF+OEQheMcqbDMgWOrJqqp4XA6G35Vz1syw=; b=qjX5Rip37hy8Ola3GNFU1fcsHzLgxM8F+mrvKNt549O4fI5zav+pT76EWe39JEezRG2DDs VEd9YFywmzJBBnSn2PkyQAOFvFKUej/ZmB18ggzJxEGWNncmChMRAdRsVrqdbkcEcrwC2X 5KvcxDk6FaXreraTDeMm5LyuCC2/DfUgXLbszTQaxIY5yeEskuDciwWiX1ORVO1Pnpdu1i qGEZjCiowGH0z4j1Qwiuo7PNSLYIc2IKCf555a+kIuix09/lxxsHaJu8Yzoy86jax1v6gj 2X5QcVJVGuQKPwibZI9p+2GI7UCpFI98MU6Opb5V4Jx4vSrroY4LqjpQ3aPOGg==
ARC-Authentication-Results: i=2; rspamd-6f98f74948-bgmcd; arc=pass ("outbound.mailhop.org:s=arc-outbound20181012:i=1"); auth=pass smtp.auth=duocircle smtp.mailfrom=waldemar@wdmsys.com
X-Sender-Id: _forwarded-from|168.235.72.19
X-MC-Relay: Forwarding
X-MailChannels-SenderId: _forwarded-from|168.235.72.19
X-MailChannels-Auth-Id: duocircle
X-Bitter-Wide-Eyed: 7aae65b7364c47ee_1699434501060_1523410569
X-MC-Loop-Signature: 1699434501060:3835348663
X-MC-Ingress-Time: 1699434501060
Received: from outbound3d.ore.mailhop.org (outbound3d.ore.mailhop.org [54.186.57.195]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384) by 100.124.29.22 (trex/6.9.2); Wed, 08 Nov 2023 09:08:21 +0000
ARC-Seal: i=1; a=rsa-sha256; t=1699434501; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=V3K9x2iEPTZsSmjGc7eip7vx0+phXe+N22E8Ka3kbEFpGl6hBgeEhShBYKOdmiAXGZi0ZC3aDXLBV Bnm4GFBnJJqWHUixAl6E4TLVAQU9RpQfROSHZoEJ0U8Oqryqjt66zZWvv2G3D5jhxVcSoWeCVRqeVa K745UNjBenUuKWTb0eGiBM/qil2Z+qtv161odcJ6YR0F96LpcvgkhIpgJhla5r+wFn+IkQvZjmje1Y nw6wNd8b5sZWzcfeDXcGX+8KipbsGpzcqU8Ts04yR5+SuBLVJMqqveeTuIZ0k50fNwe3b7Y0ADKIM/ ZeopZzQY0fyV5127qbXXp5EnTu32LSA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:content-type:subject:from:to:mime-version:date: message-id:dkim-signature:dkim-signature:from; bh=PC7twUx1UF+OEQheMcqbDMgWOrJqqp4XA6G35Vz1syw=; b=ULnbjcwKIL1qm5/Tw8JfPCurkdG3qzQmWRixJwgT4qrxMReRtgDeb7dGPobxUNBYtN2lsicsX+Pe/ rzsMKh92dCIgHII8AnxLxbEwx2LFlkiKw/hgob/EzaCXtcWKpNHIOlIPMQnIGL1miZ+slwWdOvWc6G MHb+iwJkyVGIeD6iOj35Xh+MfN0FjfHe2dMdcCoN33OJRc5thhnrGVt45srj1PbywXDiwymaQIwOX2 YA4sUlp/tCmxxNFnMpbZS1a8jA4RiKc4zfPvXutU6iPFoyEtDnM5VDiGZQ70qFrkevw7+TrX7kBhd2 LEx/KvBpAAhcZoBSz1yvAKcQcwODnXg==
ARC-Authentication-Results: i=1; outbound3.ore.mailhop.org; spf=softfail smtp.mailfrom=wdmsys.com smtp.remote-ip=168.235.72.19; dmarc=none header.from=wdmsys.com; arc=none header.oldest-pass=0;
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wdmsys.com; s=duo-1675405977089-29a98ead; h=content-transfer-encoding:content-type:subject:from:to:mime-version:date: message-id:from; bh=PC7twUx1UF+OEQheMcqbDMgWOrJqqp4XA6G35Vz1syw=; b=XNSfFQ3vMz7C6nuJqE6IwTXm58cmYA8Vpjfxlw+DOBOXra81wFvm8u645SlhF4ENkawsVMYmju9oi 24OcCmz3uKy7Owwzd04DEiJdQIXzfcfo7rDJ/SsbpvxnGVEwqQk2MLHFra6lJORQDNtusavArKqzWz Y8sMW1DBf4VvuNmc=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:content-type:subject:from:to:mime-version:date: message-id:from; bh=PC7twUx1UF+OEQheMcqbDMgWOrJqqp4XA6G35Vz1syw=; b=f9kUfVAfH29l8Upt7U2ymgGBZ2b2pz26r7YLeKtYq/MKOswUCTO1xfeEPSxXlm+v3Lx8asjazx1O2 LAD2s8Oik8uTKVlNkb2zLHSIyANNJrMiavq01FE+VubV3omSiokLoyTeYv6WYUxic0pM+tCPAtoF9T ucb1psSaas5CsVuxVVxU9m8M+W73/mzjLjNgr1+o5ck+TEibuZNSGxLpFa0Euz8rBMBAxZ67v3PpTt 749ENU6LaZe4EuV3TL3+gKchFNaIGURGBYF7krR0yzVfS50hIE33MeK23lt6hISH/iNbgeVMnvhhG9 7L1kdbaUPu88+LhNyaudFm421vtR3eg==
X-Originating-IP: 168.235.72.19
X-MHO-RoutePath: d2FsZGVtYXI=
X-MHO-User: 5baa03f4-7e16-11ee-8626-d1581f149e9f
X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information
X-Mail-Handler: DuoCircle Outbound SMTP
Received: from cmail.wdmsys.com (168-235-72-19.cloud.ramnode.com [168.235.72.19]) by outbound3.ore.mailhop.org (Halon) with ESMTPSA id 5baa03f4-7e16-11ee-8626-d1581f149e9f; Wed, 08 Nov 2023 09:08:19 +0000 (UTC)
Received: from [85.71.252.195] (helo=[10.0.0.9]) by cmail.wdmsys.com with esmtpsa (TLS1.3) tls TLS_AES_128_GCM_SHA256 (Exim 4.95) (envelope-from <waldemar@wdmsys.com>) id 1r0eXq-000cfE-Dy for v6ops@ietf.org; Wed, 08 Nov 2023 09:08:18 +0000
Message-ID: <90f07ffa-1f44-8fa6-a6eb-b35c14fcf655@wdmsys.com>
Date: Wed, 08 Nov 2023 01:08:14 -0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1
Content-Language: en-US
To: v6ops@ietf.org
From: waldemar <waldemar@wdmsys.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/3LAJ1Y00Qt19VQIkGXEByg7L3ZY>
Subject: [v6ops] IPREF as a transitioning tool
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 08 Nov 2023 09:08:50 -0000
I wanted to address one comment that I did not have time to during the session yesterday. There was a gentleman who questioned the wisdom of introducing another transition strategy. He said such a proposal would make sense 15 years ago, he also said many could propose new strategies but refrain from doing so. He ended by stating that there is no need for another transition strategy. I generally agree with the line of thought. Excessive proliferation of methods is detrimental to the cause. I questioned myself whether to go with the proposal or not. In the end I decided that IPREF is so different and so distinct from anything currently available that it should be presented. I already mentioned that it is based on a different principle which will make it succeed where existing methods would fail. There are other factors, even more significant: (a) IPREF is 100% customer premise technology. As such, its use is totally dependent on the customers choice. There is nothing IETF can do to stop them. It is similar to NAT in this respect. NAT was widely despised, still is, by IPv6 enthusiast but it took over the world in spite of attempts to block it. (b) Related to (a), enterprises love the ability to control the process themselves, without anybody dictating what they should or should not do with their networks. In addition, the economic profile hugely favors IPREF. It is simply cheaper not to do dual stacks, not to do two step transition, not to have to upgrade what they don't want to upgrade, not to have to coordinate with peers. Less cost, less risk. (c) Related to (b) the economic profile of IPREF is hugely attractive to ISPs as well. Why doing IPv4-as-a-service if it is not necessary, why burden pure IPv6 Internet with IPv4 services if they're not needed? How can IPv6 compete with IPv4 if it is required to provide extra functionality but which can be avoided? Less cost, less risk. I am just an individual, an inventor, I can do only so much. There are different roles played by different entities. IPREF must be picked up by others. By vendors to build commercial gateways, by architects and operators to complete its specification. This project is in a very vulnerable stage. It can be easily dismissed. Because of (a), (b), and (c) above, it would be foolish to do so. You must allow that the project might be picked up at some point, the gateways will be built, and in the end the economy of the method will prevail. IPv6 cause is better served embracing it than fighting it.
- [v6ops] IPREF as a transitioning tool waldemar
- Re: [v6ops] IPREF as a transitioning tool Soni "They/Them" L.
- Re: [v6ops] IPREF as a transitioning tool owen@Delong.com
- Re: [v6ops] IPREF as a transitioning tool owen@Delong.com
- Re: [v6ops] IPREF as a transitioning tool Gert Doering
- Re: [v6ops] IPREF as a transitioning tool waldemar
- Re: [v6ops] IPREF as a transitioning tool waldemar
- Re: [v6ops] IPREF as a transitioning tool jordi.palet@consulintel.es
- Re: [v6ops] IPREF as a transitioning tool waldemar
- Re: [v6ops] IPREF as a transitioning tool Vasilenko Eduard
- Re: [v6ops] IPREF as a transitioning tool Mark Andrews
- Re: [v6ops] IPREF as a transitioning tool waldemar
- Re: [v6ops] IPREF as a transitioning tool waldemar
- Re: [v6ops] IPREF as a transitioning tool Owen DeLong
- Re: [v6ops] IPREF as a transitioning tool waldemar
- Re: [v6ops] IPREF as a transitioning tool Gert Doering
- Re: [v6ops] IPREF as a transitioning tool Soni "They/Them" L.
- Re: [v6ops] IPREF as a transitioning tool Gert Doering
- Re: [v6ops] IPREF as a transitioning tool Mark Andrews
- Re: [v6ops] IPREF as a transitioning tool Martin Huněk
- Re: [v6ops] IPREF as a transitioning tool Martin Huněk
- Re: [v6ops] IPREF as a transitioning tool waldemar
- Re: [v6ops] IPREF as a transitioning tool Martin Huněk
- Re: [v6ops] IPREF as a transitioning tool waldemar
- Re: [v6ops] IPREF as a transitioning tool Gert Doering
- Re: [v6ops] IPREF as a transitioning tool Soni "They/Them" L.
- Re: [v6ops] IPREF as a transitioning tool Gert Doering
- Re: [v6ops] IPREF as a transitioning tool Soni "They/Them" L.
- Re: [v6ops] IPREF as a transitioning tool Gert Doering
- Re: [v6ops] IPREF as a transitioning tool Soni "They/Them" L.
- Re: [v6ops] IPREF as a transitioning tool Gert Doering
- Re: [v6ops] IPREF as a transitioning tool Soni "They/Them" L.
- Re: [v6ops] IPREF as a transitioning tool Gert Doering
- Re: [v6ops] IPREF as a transitioning tool Soni "They/Them" L.
- Re: [v6ops] IPREF as a transitioning tool Owen DeLong
- Re: [v6ops] IPREF as a transitioning tool Gert Doering