Re: [Int-area] [v6ops] Still need to know what has changed.... Re: IPv10 draft (was Re: FW: v6ops - New Meeting Session Request for IETF 109 - IPv10)

Khaled Omar <eng.khaled.omar@outlook.com> Fri, 25 September 2020 11:36 UTC

Return-Path: <eng.khaled.omar@outlook.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46CDB3A1384; Fri, 25 Sep 2020 04:36:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outlook.com
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 qUIjP729A6Cq; Fri, 25 Sep 2020 04:36:16 -0700 (PDT)
Received: from EUR06-AM7-obe.outbound.protection.outlook.com (mail-am7eur06olkn2064.outbound.protection.outlook.com [40.92.16.64]) (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 7FCDA3A1316; Fri, 25 Sep 2020 04:36:15 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=oJt0tulU6P3v74mQjV/bZ0Hcjy6GmaKVbXgF5TcmSe/z6kIwLDUi0+v0I7CmRK9qw/fjQUoH/s53DRMnLMwOo8Oeivnl4Dt6iJI3UKmFrpf9kzLDldGtLtwViUwja/U+4NWYDuVU9kqvMIM2Ch24/4UfaLpuXjTMwgZ0XUzcvjaBzzVBzTn7VE3Te6+5XHWLF2DsnCOdVmdRQCS8PR9p3c3TI/TMdmX7iIKy/RdcAFl1nvq6uON94ITokUNN57ihu08BBaLM5XE8Sq2Rb5c9tC4trLCGagFAcr80EGk87ZhoHbJ65pzA2OWq20C4werYtsWsDxdUDlmed2/igNO9AQ==
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=xLpVpYTUjiM9e6AbAUhbCR/T4lJs5lmlVzDap5sjZig=; b=V5D+54uWG9cS7foPVOh8bdk0+fGhj/ZIeLVqJuXAr8xVx028Ac+BmquPwO7yJnpvW/VRf1I/+UEBUYOQLHOh8xtSFfgnbRG5ryehauGYQlTcEx69ESLPXAUcRIlOLr14svZ3I954TEL4wzN2hNRlAh0JigtDU10bDeO0zj5GD2oyrDCHNV3QkIbekqfwr1cXWYjRJItRuDz5kwRHNbZHR72AqKfsj/z4NLIDQuBqPebbs3Nl54NHPlT2OVb0758iCQ15n8AH78Y5KXcA/tC50f5C/Oc24UhQmH835LTSds6muvgO8BdZfYzFCYmF5KLOc8F32BhYx3Kul0NTgKkrpg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=xLpVpYTUjiM9e6AbAUhbCR/T4lJs5lmlVzDap5sjZig=; b=VU6ogLaUDB4paEY2COil/pi0sm/gDbtYd2kmMb05AkVLAvOKUv4YBGpN0G7kwKZba+AZ2BUPmlUEu+DsmKcBHpaJh5zZo0EMAKO7UI2FNQX+jmzxXAk8Yi8uWsiywMNaysg64Eg61AlEghqp8y1FdMJ504Nvp7yud01OfN01DORXanUfA8tJWZa5HF6Yj3jmgXVIyREiGNyJK+IlW1ikD+ZaMRvzb7rRcD2GqQWSD13nFKWAZ8KOPk8tDY6o9TcbVX6tDvGZQFs+ACH/x35AU1ZCQot7mLlnf6BgIFcR1HNOzG3x8J3nlkGMM1zbxEJaefNDazwPg+Hdbv/Gbw5SFA==
Received: from AM7EUR06FT032.eop-eur06.prod.protection.outlook.com (2a01:111:e400:fc36::53) by AM7EUR06HT099.eop-eur06.prod.protection.outlook.com (2a01:111:e400:fc36::209) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3412.21; Fri, 25 Sep 2020 11:36:11 +0000
Received: from VI1P194MB0285.EURP194.PROD.OUTLOOK.COM (2a01:111:e400:fc36::48) by AM7EUR06FT032.mail.protection.outlook.com (2a01:111:e400:fc36::343) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3412.21 via Frontend Transport; Fri, 25 Sep 2020 11:36:11 +0000
Received: from VI1P194MB0285.EURP194.PROD.OUTLOOK.COM ([fe80::89f6:7540:e834:ffb8]) by VI1P194MB0285.EURP194.PROD.OUTLOOK.COM ([fe80::89f6:7540:e834:ffb8%5]) with mapi id 15.20.3412.024; Fri, 25 Sep 2020 11:36:11 +0000
From: Khaled Omar <eng.khaled.omar@outlook.com>
To: Vasilenko Eduard <vasilenko.eduard@huawei.com>, Fred Baker <fredbaker.ietf@gmail.com>
CC: "Eric Vyncke (evyncke)" <evyncke=40cisco.com@dmarc.ietf.org>, IPv6 Operations <v6ops@ietf.org>, int-area <int-area@ietf.org>
Thread-Topic: [v6ops] [Int-area] Still need to know what has changed.... Re: IPv10 draft (was Re: FW: v6ops - New Meeting Session Request for IETF 109 - IPv10)
Thread-Index: AQHWky0j5DPKSZ6F40OTLMgU9JFvQal5OFwg
Date: Fri, 25 Sep 2020 11:36:11 +0000
Message-ID: <VI1P194MB02850EAA7D945B9163C84399AE360@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM>
References: <VI1P194MB0285F47132384AC7C0D8A8DCAE3C0@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM> <F2516A37-06B1-44FC-850F-307114B7D6A5@gmail.com> <VI1P194MB0285B8AE9ACE88D1AF051ADAAE3A0@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM> <601FB9F8-DB83-4654-B652-BE07C49F7918@gmail.com> <5ab64d0ebef1402d8bf912b937d7c489@huawei.com>
In-Reply-To: <5ab64d0ebef1402d8bf912b937d7c489@huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-incomingtopheadermarker: OriginalChecksum:92A71CAD857CE03CE2030FBD54589DD5E935DBE06C5E9F108556229F03F26B55; UpperCasedChecksum:A4E577ED2A40CA16E60E4338ECEE0ABC44DA7B4758046F7EF84FD5C0D5E4F4DD; SizeAsReceived:7423; Count:44
x-tmn: [bTHG95XiDijmzFX3aWT/Dv3lPwAibW2Y]
x-ms-publictraffictype: Email
x-incomingheadercount: 44
x-eopattributedmessage: 0
x-ms-office365-filtering-correlation-id: adb15210-d83a-43c8-8420-08d8614733f4
x-ms-traffictypediagnostic: AM7EUR06HT099:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: SdHSLsjkrpoocLX+TLk/VzaM2b12jE12+a6efgrh6oLpvY4dvUMREx3gsB2aUtabxgNahjvyav/nXhpsdJCc8fEqJs16MKZ5ylO/Vk57lGWh3nvJrA559USvZ59A6vzpCSOfQql5qSeD2aHKBbWmOnHxO93XXuNzexU9mARCxYOi18jaJiqDtLkckbJNR+m9QMe8db9j/rXTxFt57Lu/7gL/glSP9YfBH3Sy7fkrUqabSebGKfp1uKyBC/9MoCnL
x-ms-exchange-antispam-messagedata: SkI0/fIZfqO8sBewdtXAswG1rbSC2CLILeZQXd5ojdowgLOLPW9JVGQPIGU3xDVjQrXMscNprou6SLJly0+uM6UYmoOU7LUID75Iq8/OOcVRbz69yIsfQqzfhBj8uLiiS70gxzHmtnqooyVG/o+U1Q==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-AuthSource: AM7EUR06FT032.eop-eur06.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: adb15210-d83a-43c8-8420-08d8614733f4
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Sep 2020 11:36:11.4090 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM7EUR06HT099
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/wr-p7aUIzjnkK26Y4OAMpRwLqeQ>
Subject: Re: [Int-area] [v6ops] Still need to know what has changed.... Re: IPv10 draft (was Re: FW: v6ops - New Meeting Session Request for IETF 109 - IPv10)
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Sep 2020 11:36:18 -0000

Hi,

From the collection of statistics you all provided, I can come to a conclusion that around an average of 40% of the world traffic became IPv6, which is still something we cannot depend on as if you compare the time since IPv6 was firstly deployed till now, I can expect that after +10 years we can come to 70 or 75% world-wide, during this time we will have blocks of IPv6 only and blocks of IPv4, which means the clear division.

That’s why looking into the transitions solutions became a mandatory or a peaceful solution such as IPv10 that will allow both version to coexist and communicate until the full migration. 

Khaled Omar

-----Original Message-----
From: Vasilenko Eduard <vasilenko.eduard@huawei.com> 
Sent: Friday, September 25, 2020 1:15 PM
To: Fred Baker <fredbaker.ietf@gmail.com>; Khaled Omar <eng.khaled.omar@outlook.com>
Cc: Eric Vyncke (evyncke) <evyncke=40cisco.com@dmarc.ietf.org>; IPv6 Operations <v6ops@ietf.org>; int-area <int-area@ietf.org>
Subject: RE: [v6ops] [Int-area] Still need to know what has changed.... Re: IPv10 draft (was Re: FW: v6ops - New Meeting Session Request for IETF 109 - IPv10)

Hi all,
Fred has formalized below something like 25% of the good White Paper!

There is one recent WP on IPv6 status: https://www.etsi.org/images/files/ETSIWhitePapers/etsi_WP35_IPv6_Best_Practices_Benefits_Transition_Challenges_and_the_Way_Forward.pdf
Where some additional facts could be found.

Eduard
> -----Original Message-----
> From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Fred Baker
> Sent: 25 сентября 2020 г. 0:45
> To: Khaled Omar <eng.khaled.omar@outlook.com>
> Cc: Eric Vyncke (evyncke) <evyncke=40cisco.com@dmarc.ietf.org>; IPv6 
> Operations <v6ops@ietf.org>; int-area <int-area@ietf.org>
> Subject: Re: [v6ops] [Int-area] Still need to know what has 
> changed.... Re: IPv10 draft (was Re: FW: v6ops - New Meeting Session 
> Request for IETF 109 - IPv10)
> 
> On Sep 21, 2020, at 3:57 AM, Khaled Omar <eng.khaled.omar@outlook.com>
> wrote:
> > Maybe if you can provide me with all the statistics I need that 
> > shows the
> deployment so I can believe.
> >
> > Khaled Omar
> 
> Sure. I'm using a site that Eric Vyncke has put together and can discuss with you.
> He uses Google (Erik Kline), Akamai (Jared Mauch), and APNIC (George 
> Michelson/Geoff Huston) numbers; there are other services that publish 
> statistics, he just hasn't included them. As of this instant, Google 
> reports that requests that come to it from 73 countries exceed at 
> least 5% of its workload from that country, and traffic from 37 
> countries exceed 35% of its workload in that country. Its Eric's site, 
> but the data is from Google, and the site can get you to Akamai and APNIC data as well for the price of a mouse-click.
> 
> What I do is download the Google statistics, select the countries that 
> exceed some cut-off, and then ask Eric's or APNIC's site to display the data.
> 
> 5% cut-off
> https://www.vyncke.org/ipv6status/compare.php?metric=p&countries=be,de
> ,in 
> ,my,gr,yt,tw,gf,vn,ch,us,fr,mx,pt,jp,lu,br,th,fi,mq,uy,gb,ec,ee,lk,ca,
> hu,ae,gp,re, 
> nl,tt,ie,au,nz,pe,sa,ga,bo,ro,at,gt,no,ph,cz,sg,il,mo,pl,ar,sx,tg,si,n
> p,mm,om,bt,k r,ke,fo,co,md,zw,cg,pr,is,lv,am,se,ru,li,jo,sk
> 
> 35% cut-off
> https://www.vyncke.org/ipv6status/compare.php?metric=p&countries=be,de
> ,in ,my,gr,yt,tw,gf,vn,ch,us,fr,mx,pt,jp,lu,br
> 
> APNIC's display of its data on India is interesting 
> https://stats.labs.apnic.net/ipv6/CC?x=1&s=1&p=1&w=30&c=IN
> 
> If you scroll down, you will get a break-out by AS. APNIC reports that 
> customers from 12 ASs use IPv6 when accessing APNIC with 50%+ 
> probability ("ipv6- capable" and carrying that amount of data), and 
> given a choice of IPv6 or IPv4, most of them are "ipv6-preferred" (eg, 
> use IPv6 when given a choice). But about
> 50 ASs actually have users *using* IPv6 for some subset of their 
> workload. In a Financial Times blog a week or two ago, the chair of 
> India's IPv6 deployment task force argued that it should have an 
> IPv6-only DNS Root Server on the basis of its IPv6 deployment and 
> usage. I disagree with him (remarks available on request; they only 
> have 38 IPv6-capable root servers in country), but the basis for the argument was interesting.
> 
> I think the APNIC data is interesting because it crosses the backbone. 
> Google and Akamai run CDNs, which means that traffic can be between a 
> residential subscriber and its CDN server without materially touching 
> the ISP. APNIC runs no CDN, which means that traffic has to *also* 
> traverse the ISP and the backbone to APNIC - there is and end-to-end path across the backbone. Think about this:
> when a user accesses a service using IPv6 (or IPv4 for that matter), 
> the packet has to go from his computer, IOT device, or telephone to 
> the site in question and the response has to come back; there has to 
> be a complete end-to-end path in each direction. Miss one IPv6 
> connection in one direction, and it may as well be IPv4-only, because that's the only thing the end system will use.
> 
> From 73 countries, there is an end-to-end path of sufficient strength 
> that a significant proportion of data *can* traverse it using IPv6, 
> and the end system - which chooses whether to use IPv4 or IPv6 - will *choose* IPv6.
> 
> My search engine tells me "There are 195 countries in the world today. 
> This total comprises 193 countries that are member states of the 
> United Nations and 2 countries that are non-member observer states: 
> the Holy See and the State of Palestine." 37% of them, 73, have significant IPv6 usage.
> 
> Define "widely deployed"? I'll add "and used?" That's pretty wide, in my book.
> 
> What prevents this from being IPv6-only? Computers and network 
> equipment used by residential and enterprise subscribers have 
> supported both IPv4 and IPv6 for years. The most commonly used applications are quite happy with either.
> The issue I see is primarily enterprise lack of IPv6 adoption in its 
> customer-facing services. Even an "IPv6-preferred" site will use IPv4 
> when talking with something that will only use IPv4.
> 
> There is nothing proprietary here. Forward if you like.
> 
> >  From: Fred Baker <fredbaker.ietf@gmail.com>
> > Sent: Monday, September 21, 2020 4:49 AM
> > To: Khaled Omar <eng.khaled.omar@outlook.com>
> > Cc: Erik Kline <ek.ietf@gmail.com>; Eric Vyncke (evyncke) 
> > <evyncke=40cisco.com@dmarc.ietf.org>; int-area <int-area@ietf.org>; 
> > intarea-chairs@ietf.org
> > Subject: Re: [Int-area] Still need to know what has changed.... Re:
> > IPv10 draft (was Re: FW: [v6ops] v6ops - New Meeting Session Request 
> > for IETF 109 - IPv10)
> >
> > Boy. If “millions and billions” isn’t wide deployment, maybe I need 
> > to go back
> to grammar school.
> >
> > Sent from my iPad
> >
> >
> > On Sep 19, 2020, at 4:18 PM, Khaled Omar 
> > <eng.khaled.omar@outlook.com>
> wrote:
> >
> > 
> > But none of these transitioning solutions are widely deployed, maybe 
> > it is IPv10 time ;-)
> >
> > Khaled Omar
> >
> > From: Erik Kline <ek.ietf@gmail.com>
> > Sent: Sunday, September 20, 2020 1:05 AM
> > To: Khaled Omar <eng.khaled.omar@outlook.com>
> > Cc: Fred Baker <fredbaker.ietf@gmail.com>; Eric Vyncke (evyncke) 
> > <evyncke=40cisco.com@dmarc.ietf.org>; int-area <int-area@ietf.org>; 
> > intarea-chairs@ietf.org
> > Subject: Re: [Int-area] Still need to know what has changed.... Re:
> > IPv10 draft (was Re: FW: [v6ops] v6ops - New Meeting Session Request 
> > for IETF 109 - IPv10)
> >
> > As noted before: RFCs 6052, 6146, 6147, 6877, 7915, and others 
> > comprise the
> solution deployed to literally hundreds of millions if not billions of 
> mobile devices and numerous access networks worldwide.
> >
> > On Fri, Sep 18, 2020 at 5:24 AM Khaled Omar
> <eng.khaled.omar@outlook.com> wrote:
> > >> Who are these “many people”, and what problem do they see being
> solved?
> >
> > Network engineers everywhere, they are waiting for the announcement 
> > of an
> official robust solution to the depletion of the IPv4 address space 
> and the division that occurs recently on the Internet.
> >
> > People read the draft and many wrote about it because the idea is 
> > simple and
> requires no intervention from their side, that’s why I ask the IETF to 
> take the draft seriously and put personal benefits aside for now, as 
> LATER everything will back to normal, believe me, all are in need for this.
> >
> > Khaled Omar
> >
> > -----Original Message-----
> > From: Fred Baker <fredbaker.ietf@gmail.com>
> > Sent: Friday, September 18, 2020 12:24 PM
> > To: Khaled Omar <eng.khaled.omar@outlook.com>
> > Cc: Roland Bless <roland.bless@kit.edu>; Eric Vyncke (evyncke) 
> > <evyncke=40cisco.com@dmarc.ietf.org>; int-area <int-area@ietf.org>; 
> > intarea-chairs@ietf.org
> > Subject: Re: [Int-area] Still need to know what has changed.... Re:
> > IPv10 draft (was Re: FW: [v6ops] v6ops - New Meeting Session Request 
> > for IETF 109 - IPv10)
> >
> >
> >
> > Sent from my iPad
> >
> > > On Sep 17, 2020, at 2:08 PM, Khaled Omar
> <eng.khaled.omar@outlook.com> wrote:
> > >
> > > Regarding the confusion, the community is curious about the idea, 
> > > many
> people support it as it solves the problem that they think they are not part of it.
> >
> > This statement has me a little confused. I see a lot of commentary, 
> > but I don’t see people commenting along those lines. I frankly see 
> > commentary similar to what I sent you declining a v6ops slot,
> >
> > Who are these “many people”, and what problem do they see being solved?
> > _______________________________________________
> > Int-area mailing list
> > Int-area@ietf.org
> > https://www.ietf.org/mailman/listinfo/int-area
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops