IETF Logo Mail Archive

Re: ipv4 and ipv6 Coexistence.

"Eric Vyncke (evyncke)" <evyncke@cisco.com> Wed, 19 February 2020 22:05 UTC

Return-Path: <evyncke@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C045A12083D for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2020 14:05:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=KAU883Ll; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=qwEb2W13
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 kIX2UOjiQg1w for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2020 14:05:27 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2F88120020 for <ietf@ietf.org>; Wed, 19 Feb 2020 14:05:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=21415; q=dns/txt; s=iport; t=1582149926; x=1583359526; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=vXcGLkatddkSfxDPSfWNPHcGyaGHL3cqsU1jnUDiUU0=; b=KAU883Ll4ilrBbVUTOxVCB26rQpLMOV7SOP/28jmkC4vRmAfeb4MdaAM oYLreIzmAVIqnCbvw1uLHbeYltJIHrMbhSmRoQx0tbS5c/BUAiDmt938s SKZgQ+UrYdy546TNvnSsL/7VfREoPuE8n/jXimyE8TC4iAgqmqI6RCSSM U=;
X-IPAS-Result: A0B6AwA6sE1e/40NJK1mGwEBAQEBAQEFAQEBEQEBAwMBAQGBe4ElL1AFbFggBAsqhBSDRgOKcII6JYliiU6EYYJSA1QJAQEBDAEBGAEFDwIEAQGEQAIXgW0kOBMCAwEBAQMCAwEBAQEFAQEBAgEFBG2FNwyFZgEBAQECAQERER0BATcBCwQCAQgOAwMBAQEBJwMCAgIfBwoUCQgBAQQBDQUbBAOCfwQBAYF9TQMOIAEOo0QCgTmIYnWBMoE7gUQBAQWBLwEDAwIOGGaCbg0LggwDBoE4jCQagUE/gTgMFIFOfj6CG0kBAgGCAw0JgloygiyOHYJGhXCYTDJECoI7h0+JMYEqhDYcmyuOb4h5gi6QHgIEAgQFAg4BAQWBaSINgUtwFWUBgg0BMxI+GA2OHYNzhRSFP3QCgSeNagEB
IronPort-PHdr: 9a23:dXj3kBFxPyYTV8+ygrc+351GYnJ96bzpIg4Y7IYmgLtSc6Oluo7vJ1Hb+e4z1A3SRYuO7fVChqKWqK3mVWEaqbe5+HEZON0pNVcejNkO2QkpAcqLE0r+efP0fioxH8lqX15+9Hb9Ok9QS46nPQ/Ir3a/7CAfFlDkLQQlerbTHYjfx4Svzeeu9pbPYgJOwj2gfbd1KxbwpgLU5IEdgJBpLeA6zR6BrnxFYKxQwn8gKV+Inhn679u9mfwr6ylKvvM968NMGb73eag1V/RYCy86KCE4
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.70,462,1574121600"; d="scan'208,217";a="419229426"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 19 Feb 2020 22:05:25 +0000
Received: from XCH-ALN-001.cisco.com (xch-aln-001.cisco.com [173.36.7.11]) by alln-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id 01JM5PjN005943 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 19 Feb 2020 22:05:25 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-ALN-001.cisco.com (173.36.7.11) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 19 Feb 2020 16:05:25 -0600
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 19 Feb 2020 17:05:24 -0500
Received: from NAM11-BN8-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 19 Feb 2020 16:05:24 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=CGkP4naz2a2BaQ0JR0vg4p3a5RH3pa1JRwxq8vA65LtaDyvMyFPBkhbqda2ZeBYCmjVwiDHdZPdoHTYHJ9ZlMNINxaPLeO37C0Ty35ZkwgclogdgzzsWDgKjj7pxwJVSgIT8747lRNH9zt+Lulce/uakfsV2nsO5AnxOevWwiDo+BqkdX8riCmPu/vz8KaTlIe1LkBYxkr++sSVqJ/W+cvG+Is3dAtv0FpEmggEkMtcGRRV7OGm5sw+CUac91SkTDiiTmAJCXKYnGI8j4NVwt0fZbgsMYRpio1zqKRT45jfk/hD9MyGxfIXIx/4Lk/0V7ZefqmBlZu7aBFXNvbZsJw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=vXcGLkatddkSfxDPSfWNPHcGyaGHL3cqsU1jnUDiUU0=; b=I6dgTmmX0JFt+2OSn+qK38FqqSzBQ7rvBcO1w/GofqBTNn1BV1s6A6Cepeqvq7EOOa9gF6O+VjYJjeXG0xTAMRwKqn+wrZLdVVW2BfoL24Z9NZoaZf6WV1g5O5aCfM+Qv7F9czCf9ITb+nXpAzXbu/3bdDS8d5iQ5uhKWdtoiN2bqsHNrPKyoVdVfNJsb9eVEsyYP0IhpjoixdN9FpLxrqoNB6I2addpr74SJqXEcaeRQa0aU8jL6lrCrRoW1SDtstBqg25BUAhXxiWIrPsTaylB4kMCvTXktsMQbhztji0tdCjD7nJcTuci8Amw4wBSuFWBXbAPGY7mB9V46g30tQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=vXcGLkatddkSfxDPSfWNPHcGyaGHL3cqsU1jnUDiUU0=; b=qwEb2W13NVcSvPkPxN/baND7X2qv5ryued/SgWnTi3W+8BAWFc+tfSKKKoM8YlxTuipTdJXBu8D79OmgJuT/0M0zE5DVagemiepj2pt3OPzMYG34hzf76iA2DUnsfikd89pHJTkMTet28WYUuEa9WGwDhtGge3uF/A4zp80kEv4=
Received: from DM5PR11MB1753.namprd11.prod.outlook.com (10.175.88.141) by DM5PR11MB0027.namprd11.prod.outlook.com (10.164.155.33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2750.17; Wed, 19 Feb 2020 22:05:23 +0000
Received: from DM5PR11MB1753.namprd11.prod.outlook.com ([fe80::680d:e22e:72d5:67ca]) by DM5PR11MB1753.namprd11.prod.outlook.com ([fe80::680d:e22e:72d5:67ca%3]) with mapi id 15.20.2729.032; Wed, 19 Feb 2020 22:05:23 +0000
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: Khaled Omar <eng.khaled.omar@outlook.com>, Erik Nygren <erik+ietf@nygren.org>
CC: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: ipv4 and ipv6 Coexistence.
Thread-Topic: ipv4 and ipv6 Coexistence.
Thread-Index: AdXnL4CMqKHMj241QNOLcaD05q7rXAAFTlYAAAFd+RAAAorKAAAAL5oAAAj9HwA=
Date: Wed, 19 Feb 2020 22:05:22 +0000
Message-ID: <4A81B34F-4797-4D50-89A1-0451577D6C3E@cisco.com>
References: <PR3P194MB0843ACAE01F33CEC57266A1AAE100@PR3P194MB0843.EURP194.PROD.OUTLOOK.COM> <CAL9jLab3GN5eEwbC1cHQkG9onUn5rry7OMykQ7MiRGo90TKizg@mail.gmail.com> <PR3P194MB08432397118C0AB443EC7611AE100@PR3P194MB0843.EURP194.PROD.OUTLOOK.COM> <CAKC-DJjJbq_pD4uX75gBSEDzgtH8inVx8eh9FLqbYF6ikzcU=w@mail.gmail.com> <PR3P194MB084377C2F7094BDFE05A3A88AE100@PR3P194MB0843.EURP194.PROD.OUTLOOK.COM>
In-Reply-To: <PR3P194MB084377C2F7094BDFE05A3A88AE100@PR3P194MB0843.EURP194.PROD.OUTLOOK.COM>
Accept-Language: fr-BE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.22.0.200209
authentication-results: spf=none (sender IP is ) smtp.mailfrom=evyncke@cisco.com;
x-originating-ip: [2001:420:c0c1:36:9994:8a6f:a879:1893]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: bd9f6b13-451c-456d-b81a-08d7b587d133
x-ms-traffictypediagnostic: DM5PR11MB0027:
x-microsoft-antispam-prvs: <DM5PR11MB002709C28C0E8559E57F1004A9100@DM5PR11MB0027.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7691;
x-forefront-prvs: 0318501FAE
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(39860400002)(136003)(366004)(396003)(376002)(346002)(189003)(199004)(110136005)(316002)(36756003)(91956017)(64756008)(66476007)(66946007)(71200400001)(45080400002)(478600001)(6506007)(33656002)(66446008)(53546011)(66556008)(76116006)(86362001)(2906002)(966005)(2616005)(21615005)(8676002)(186003)(6486002)(8936002)(6512007)(66574012)(5660300002)(81166006)(81156014)(4326008); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR11MB0027; H:DM5PR11MB1753.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: ehTLVSznxmFTUAH971iXzPnVl36iVO2j4S3Aqjnt+c0GwjXJYSJN3Lmvbo8bZZkrdz8lacrAhYjRZ7T4kgFMe3zlwR2JMoVZfLGrDDa+tqK+uAMqg0mCtWnDdIUrQpJ43cGnO5JFMPNo0oqa0d3hVtPGMkNhf7HefUx0Yd9GHQjnPw2eb3cdK5ON7ynZaNVrYhUJ3HVfo59wsFTRjBgTWbOmwgfDyq2AltbKMTPRsu6WVw2gpypRuEky7BB8HHlilN3JO4yLGOqWq5B0G4mbOGwEC4ZdvwOums+Lw96j24ZzHOMb3TN75kgqYmcKXcG931Yu/qAwxSO+PUvgbYFPtvW4XECdPzu56mPDBOPc39xgh9hBPbESfYEwsdqFQmo87LVLKYBY8RVTv4OpA2moZsZbgTInUJeKvQdrZiIF/e8LrBzd8a4Qv7Me3zyxoBLdInZSIKFpOd/HW8lrYfrVcTobKhOXm1gmZCxEFX81tntfgqGg+43DhGOtHeqB4AfzutDC51w+0FX75zgCuKhJnA==
x-ms-exchange-antispam-messagedata: xQZ0x21PN7yK6mwtiDlX8XMuD+M39w7gWI1qc4mOq57HNZDAUnn4qCnXPUDQxbo0KlR1eP4MLqDuYEbJC8tg7ON1mnJn7yje+JeYhB0ncofa7pMG+BUZROE7teHvqGSQrE/mn/avYq0+3VTBNJAiEaUfLwNR74zPBFzlLBdOVZ5Q7XWSUwt4cAqXaVT+CY+S1aGICZd0QfUp9Q6VUhxoSQ==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_4A81B34F47974D5089A10451577D6C3Eciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: bd9f6b13-451c-456d-b81a-08d7b587d133
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Feb 2020 22:05:23.0045 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 1aw0pH2v1uPOahqxrogeJBpTL4Bidt/kjwjlJFQE0hhgwcIOYeU4QzPOe7lWi3+sszzSDwwuBK1hE4hiWUImUA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR11MB0027
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.11, xch-aln-001.cisco.com
X-Outbound-Node: alln-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NrX_F4u1-GoVBHjett30BOEIccc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2020 22:05:30 -0000

IPv6 deployment takes indeed longer than most of us had hoped for...

In several countries, more than half of the Internet users use IPv6 daily (less in enterprise deployment). ISPs in my country, Belgium, see between 30% to 40% of their traffic being IPv6 (mainly to the big content providers).

Khaled, I will anyway follow your advice and won’t waste my time anymore on this thread ;-)

Regards and thank you for your interest in keeping the Internet up and running

-éric

From: ietf <ietf-bounces@ietf.org> on behalf of Khaled Omar <eng.khaled.omar@outlook.com>
Date: Wednesday, 19 February 2020 at 19:51
To: Erik Nygren <erik+ietf@nygren.org>
Cc: IETF Rinse Repeat <ietf@ietf.org>
Subject: RE: ipv4 and ipv6 Coexistence.

Ok, I think I got the answer for my question, don’t want to waste your time.

Waiting and watching for a better solution to be applied practically.

Khaled Omar

From: Erik Nygren <erik+ietf@nygren.org>
Sent: Wednesday, February 19, 2020 8:43 PM
To: Khaled Omar <eng.khaled.omar@outlook.com>
Cc: Christopher Morrow <morrowc.lists@gmail.com>; IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: ipv4 and ipv6 Coexistence.

It really is a composite story of individual ISPs, devices, and content.
Some stats I published two years ago from the perspective of one CDN:
https://blogs.akamai.com/2018/06/six-years-since-world-ipv6-launch-entering-the-majority-phases.html

and things have grown since.  For example, Akamai just peaked at 21 Tbps of global IPv6 traffic delivered:
https://blogs.akamai.com/2020/02/at-21-tbps-reaching-new-levels-of-ipv6-traffic.html

During a peak like that, some large countries and customers
can see a majority of traffic being IPv6.  You can see some of the wide
variation between ISPs here:
  https://www.akamai.com/us/en/resources/our-thinking/state-of-the-internet-report/state-of-the-internet-ipv6-adoption-visualization.jsp#networks

(There are also a few consumer electronics devices holding the numbers down
in large residential networks.)

         Erik




On Wed, Feb 19, 2020 at 12:35 PM Khaled Omar <eng.khaled.omar@outlook.com<mailto:eng.khaled.omar@outlook.com>> wrote:
>> these numbers are ~2yrs old... but 25% is not "almost nobody".

Actually, devilations in percentages makes things worse, some think it is 25% others think it is 30% others think no IPv6 at all :) and all these percentages are incorrect because only one thing can make it clear, to find an official solution announced for everybody stating that what should we do in such situation.

Best Regards,

Khaled Omar

-----Original Message-----
From: Christopher Morrow <morrowc.lists@gmail.com<mailto:morrowc.lists@gmail.com>>
Sent: Wednesday, February 19, 2020 6:51 PM
To: Khaled Omar <eng.khaled.omar@outlook.com<mailto:eng.khaled.omar@outlook.com>>
Cc: IETF Rinse Repeat <ietf@ietf.org<mailto:ietf@ietf.org>>
Subject: Re: ipv4 and ipv6 Coexistence.

On Wed, Feb 19, 2020 at 9:28 AM Khaled Omar <eng.khaled.omar@outlook.com<mailto:eng.khaled.omar@outlook.com>> wrote:

>
> From what I see in the real world, IPv4 still dominating and almost nobody started using IPv6, and also, I didn’t find any solution applied practically in today’s networks for this issue.
>

I don't think it's accurate to say: "almost nobody started using ipv6"

https://www.internetsociety.org/resources/2018/state-of-ipv6-deployment-2018/

these numbers are ~2yrs old... but 25% is not "almost nobody".

v2.23.0 | Report a Bug | By Email