Re: ipv4 and ipv6 Coexistence.

Khaled Omar <> Thu, 20 February 2020 03:24 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B5AE71200C1 for <>; Wed, 19 Feb 2020 19:24:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.998
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id e5x0cGeLuc9E for <>; Wed, 19 Feb 2020 19:24:10 -0800 (PST)
Received: from ( [IPv6:2a01:111:f400:7d00::82d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C8FAA12002E for <>; Wed, 19 Feb 2020 19:24:09 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901;; cv=none; b=MIiG+2slewY9x/wgIWOGGXHDUtWmqmla3pKIolwN7TDCEQvo/eKS4UMH5ijWonbRYQubxZgfMEfg1y/hYrsylF47mbG7JbCf0HUPsIkaCrebDYC3cqu0zc1z0j7pGZLZyD3VhF7HAq6OwGgtAfJJYqspueFNtDtJvPKTLhfVQDR5hqIJmcCpndEajnAxpQHB66hQlsOiXyShfLYTFpM0oddRS7TsJsIfrP1+QW9C5cvYiJMa3CFun66b1eiSWGtRQgvGhX707pxqM+TifAHd5vsm8u+IorI5+kFQHMrmAveefLq+OUdcwwezCXTZMDSuHZMcxVw7s9IGa6UL6x4dag==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed;; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=FwSBhV1VpNfu5k8ol4hEW3cWvGVaX2RxlZeGXmwDM18=; b=fRWFRM1TEX5biQYNAIWGLC0D/Qahr6RiDSUCIwT8nXhe9hznxvhvR3Uw2Hq2C92G8HYKWO23msRgwuz+0bh9IlVaIIvM4mqzl4WHNkg5UOdsWmQfKZadxS+n4kzgMlEX9HgPL+1PdAtoIR5yYW/5TtbKoz8/RxrfgJMGtgUZiqBXKDwECxIJLIxPbcBNuzbguS89AT8el4oZp8zz01acJkwP+GW5wTZ+CShiRZVOLwIt94X9/Z+aZgGLchgD/6lVIvhzmsQ7Rj0TGQ69c7tAHXNqGpCcyVYRFDrCrO4lCP50vWEZsTzXgFHwrJ/hqFHfadF0DGMLV77Yc9Lh0kWetA==
ARC-Authentication-Results: i=1; 1; spf=none; dmarc=none; dkim=none; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=FwSBhV1VpNfu5k8ol4hEW3cWvGVaX2RxlZeGXmwDM18=; b=ffSO0j3HhW7yA0WGAPTTOtKUl4ewEhZLu3bQMWYVTy772wrRIRKFtMD1QOc7LzYs2E4Z867EIHBYUT5Er2aIqtIw4keVHdsIFqHDWu5vSbsvqxADbwgoVe28HtBkr42ZW6mDlFOshX9sdjNFqvCJBog3cr5TtaAIEfyjfcSQi6X/xazlyQWzmNabVqBaFcTt6oDQWC2szb1B3MqfUX4kp/Dmur3sa7b/Rr8kZhr5WTBVMePmULXNvHdiygG0thqTREgtTThU++z9hNZqMsBKYsuKNDXkHBcYrs2MfllLU36d6AI3bir/A7+BhLkhnbOfvLbxbNNtXlk4oHauzzWPTA==
Received: from (2a01:111:e400:fc11::39) by (2a01:111:e400:fc11::218) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2750.18; Thu, 20 Feb 2020 03:24:07 +0000
Received: from PR3P194MB0843.EURP194.PROD.OUTLOOK.COM ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2750.18 via Frontend Transport; Thu, 20 Feb 2020 03:24:07 +0000
Received: from PR3P194MB0843.EURP194.PROD.OUTLOOK.COM ([fe80::b428:e305:c763:c9a3]) by PR3P194MB0843.EURP194.PROD.OUTLOOK.COM ([fe80::b428:e305:c763:c9a3%5]) with mapi id 15.20.2729.033; Thu, 20 Feb 2020 03:24:06 +0000
From: Khaled Omar <>
To: JORDI PALET MARTINEZ <>, Victor Kuarsingh <>
CC: IETF Rinse Repeat <>
Subject: Re: ipv4 and ipv6 Coexistence.
Thread-Topic: ipv4 and ipv6 Coexistence.
Date: Thu, 20 Feb 2020 03:24:06 +0000
Message-ID: <PR3P194MB084363D11F21507C295134FCAE130@PR3P194MB0843.EURP194.PROD.OUTLOOK.COM>
References: <PR3P194MB0843ACAE01F33CEC57266A1AAE100@PR3P194MB0843.EURP194.PROD.OUTLOOK.COM> <> <PR3P194MB08431E138262F2A43C1D0621AE100@PR3P194MB0843.EURP194.PROD.OUTLOOK.COM> <> <PR3P194MB0843939F3B38426960A66E70AE130@PR3P194MB0843.EURP194.PROD.OUTLOOK.COM> <> <> <PR3P194MB0843112CA5B461547C294CE7AE130@PR3P194MB0843.EURP194.PROD.OUTLOOK.COM>, <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-incomingtopheadermarker: OriginalChecksum:68BA6BC8B768297DAB692DCF73CA64C1CD1D2FC6A171E3BC03DC6DC597D24865; UpperCasedChecksum:8F90E75BF1284609E8A5DB52058ADAF4F63C935F88ED22D4A858AC9655CBA385; SizeAsReceived:7540; Count:45
x-tmn: [elqVBiGjS5prhzn2vCos2jm80cu1ZLlR]
x-ms-publictraffictype: Email
x-incomingheadercount: 45
x-eopattributedmessage: 0
x-ms-office365-filtering-correlation-id: faf82dc1-4f7b-4ec7-8586-08d7b5b457bd
x-ms-traffictypediagnostic: AM6EUR05HT219:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: Qci0DIzNjBaGD+rRVPsuH+ba5c6IJHxKexZzDKxVStU3dLsrecUzSTwiSQGwgjopup/Qb4zQQBsI5mWKox9XNQA02iX5MndVU2ogoKcwvEswlYsf1DTW3oQ8dRKeguX0PgWWAT3BWG5EoMnDX0y8hMcET2MCdwWXIgnclTNeW5fp9eni9Nrh9aqN6DCBYM8TjfoB8+0cI+hq7jdsuWbpfzM5zCpRVwQ68fAvT+vmY+k=
x-ms-exchange-antispam-messagedata: L3u956bPD21ynBB81Fw2A+ooTO6HYT3Bj0EmchpygZH9zm0ZzfpewrGii45vrjm5ebhX4qn4rpgEejU8pV/QbZatR2VDLilBU1RHgP+L9mkuBEDVIZL5wTUX9IF6ac6wWAjgrFoqmzIAfR87iREH/Q==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_PR3P194MB084363D11F21507C295134FCAE130PR3P194MB0843EURP_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: faf82dc1-4f7b-4ec7-8586-08d7b5b457bd
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Feb 2020 03:24:06.5848 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM6EUR05HT219
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 20 Feb 2020 03:24:14 -0000

I understand, but leaving things going worse is not acceptable, internet users will blame you when they feel the division on the internet, and you will only blame yourself for not keeping trying, at least, let people know you tried to find a solution that doesn't requires their involvement even if it will not be used, let them ask and find the best that suits them with less efforts, but remember, it will be late.

Get Outlook for Android<>

From: Victor Kuarsingh <>
Sent: Thursday, February 20, 2020 5:06:14 AM
To: Khaled Omar <>
Cc: IETF Rinse Repeat <>rg>; JORDI PALET MARTINEZ <>
Subject: Re: ipv4 and ipv6 Coexistence.


I am certainly not intending to stop anyone from inventing anything or working on things.  I am just sharing an opinion based on experience.

We have historical experience that seems to indicate that a one-size-fits-all approach is difficult for a number of technical and operational reasons.  The Internet is a highly distributed system where each network operator gets to decide for themselves what they need and want.  I am also yet to see any two networks which manifest identical requirements.  So any attempt to convince everyone to adopt an all-in-one solution will likely be difficult to apply to all uses cases or the general use case.

There has been a long list of transition technologies developed, none of which fit all uses cases which is likely ok.    The largest barrier I see at this point, which will apply to those slow to adopt IPv6, and have anyone who has already enabled a transition technology, is cost (economics).  Any solution which requires people to re-invest money (even if a new solution is better) will likely be met with opposition given competing requirements and opportunity cost.

To exemplify, if I was an operator who enabled transition technology X which operated moderately well.  If presented with the option to enable a new technology Y, which is definitely better, but would bare significant deployment time and costs, I would likely not action it since I would be giving up an opportunity to spend that time and money on other functions.

For those whom have not enabled IPv6 yet, there may be some economic or other practical reason to overcome to get them to adopt a solution.


Victor K

On Wed, Feb 19, 2020 at 9:45 PM Khaled Omar <<>> wrote:
What i meant is that if you have nothing to add then don't stop what others are trying to do, keep working on what you are trying to do even if it didn't work for long time but you believe on it, but as long as our one goal is to find a solution then the end result will be good for all ones leaving the stoppers aside.

Get Outlook for Android<>

From: Victor Kuarsingh <<>>
Sent: Thursday, February 20, 2020 4:29:43 AM
To: Mark Andrews <<>>
Cc: Khaled Omar <<>>; IETF Rinse Repeat <<>>; JORDI PALET MARTINEZ <<>>
Subject: Re: ipv4 and ipv6 Coexistence.

 The sad reality is anyone whom is responsible to build, expand or manage a network needs to deal with the IPv4 long tail connectivity needs.

I would agree with Mark's comment related to the notion we have enough transition technologies today.  As far as I can see, anyone who needed to deploy IPv6 and/or create a pathway to legacy IPv4 has been able to do so (perhaps there are corner cases, but I would say for the vast majority, they could do what they needed to do).

As for the governments intervening, I am not so sure about that, but I am not opposed (just don't think it will work). Bureaucracy rarely solves what turns out to be a fundamental market problem.


Victor K

On Wed, Feb 19, 2020 at 8:27 PM Mark Andrews <<>> wrote:
Really we do not need to be inventing anything new in this space.
We already have too many mechanisms.  ISPs just need to DEPLOY the
existing mechanism.

We have plain dual stack.

We have public IPv4 + 6rd for ISPs where the access network doesn’t
support IPv6.

We have CGN + 6RD + 100.64/10 for ISPs where the access network doesn’t
support IPv6 and they have run out of IPv4 space.

We have DS-Lite, MAP-E, MAP-T, NAT64 … providing IPV4AAS for when the ISP
has run out of IPv4 and the access network supports IPv6.

We have CGN + IPv6.

Do we really need something more at the protocol level?

We do need Governments to ban the selling of new IPv4-only domestic
devices (CPE routers, TV’s, game boxes, etc.).


> On 20 Feb 2020, at 11:32, Khaled Omar <<>> wrote:
> Regardless the different %s, lets take the average one, it can not make us optimistic and stop thinking about a better solution, we should learn from the long time passed without full migration occured, if we will wait till that happens, the division will occur which is not good for the internet, lets welcome new ideas and give it the space, time, and opportunity fairly, if it will be good then welcome, if not, trash is made for this.
> Get Outlook for Android
> From: ietf <<>> on behalf of JORDI PALET MARTINEZ <<>>
> Sent: Thursday, February 20, 2020 2:00:58 AM
> To: IETF Rinse Repeat <<>>
> Subject: Re: ipv4 and ipv6 Coexistence.
> And you're missing several points about how those stats are looked at.
> The % in the stats shown by google/others is only what they can measure, but they can't measure *all*. There are countries (big ones) that don't allow measurements, or at least the same level of details, and however, are doing massive IPv6 deployments.
> All the CDNs and caches have IPv6. The customers that have those caches and enable IPv6 for their subscribers, are getting ranges over 65%, sometimes even up to 85-90% of IPv6 traffic when mainly the subscribers are householders instead of big enterprises.
> Also, the google (and others) measurements, show average worldwide, but if you look to many countries they have even surpassed the 50% or so.
> Regards,
> Jordi
> @jordipalet
> El 20/2/20 5:38, "ietf en nombre de Khaled Omar" <<> en nombre de<>> escribió:
>     Since long time I was observing this, still almost the same, no clear progress occurred.
>     Thanks,
>     Khaled Omar
>     -----Original Message-----
>     From: Scott O. Bradner <<>>
>     Sent: Wednesday, February 19, 2020 8:11 PM
>     To: Khaled Omar <<>>
>     Cc: IETF Rinse Repeat <<>>
>     Subject: Re: ipv4 and ipv6 Coexistence.
>     Quite a few folk are already there - see
>     Scott
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> 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.

Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET:<>