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)

Khaled Omar <eng.khaled.omar@outlook.com> Thu, 24 September 2020 21:59 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 824EC3A0544; Thu, 24 Sep 2020 14:59:31 -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=unavailable 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 etvNLrV8Swqq; Thu, 24 Sep 2020 14:59:29 -0700 (PDT)
Received: from EUR04-VI1-obe.outbound.protection.outlook.com (mail-oln040092075020.outbound.protection.outlook.com [40.92.75.20]) (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 3F3283A046A; Thu, 24 Sep 2020 14:59:29 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=XHMXOGpYohlhdJweoVddUgVh/RzaxtxGuv/PtsdQwvQB8Mt8t2aDvaL1CIGzfatD2s9n75C1GGL+/5k8hH3tuSWQBAsz4ROhqIF38ANWrqR+iOQWQxqjL1ds7+6hGdS7cG08w53EoFm85jq0ZshyW4kN4yq03oXehJk6ONMREnh72AaOSoammGBlMD19BnBkDE0iwAJls5jL4QCp/V1AslhZFMS6F20oUl1Q3ivq62x8RRZAWDbJqMwKXwKRYEFGdPjCo2Lk2Z3myXOWBwvlyN4jsc/5keKYhMU2jak2jEgp0t5bzHi6ZdW/nHElod9vtN0aI3zfbRh9S4ZHQ+b4Wg==
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=+wIolE6IvzIIFugW3L184QgoKOqM6iFzqdhPBAeWmso=; b=avhuC7ZTfctEcr43tRzrz4uYS08PinQ7joA3ytimW864KNv00Za0TQb56Nf3axE3knHGq2o1ohaCUu0U4sZnOlRa9kLuNYX+56W2cG51k2PLeGM/K8FCbhsf3c+o/rn2VISneNL7LWyNXdxcRHHFI0lJOXQpSUollmQQE1O5sWxE8LuD3WHC5N3GeUvTkJBoZIxPSEmQvouUv8qhBSTTUqcOo1zk2QK+uF4wgUbQRPhEv/sUj7Q9+iiO8TBpoKRt759JUYBs34PHtms942tLcA3X272GLi0kdcC0cRom5w4vr23PLYtOvyM0usa3JReEsDJupNTLw+0gDqBVVH08MQ==
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=+wIolE6IvzIIFugW3L184QgoKOqM6iFzqdhPBAeWmso=; b=WsJzA0ULTgIrh2WzcrHLtB0qiPWpAsBnnO/AmEU64nyeeoBBBOuw1jV+KokBli6RI+3TYzUXO0m9jdIzp5cVpqUqRfYPmJctqrLV62VEtZ1Q142oywbu9/xJP0RHO1uFiyEINioCiSNsLYEFAuevH4adygT+kOIQ4nkl2LxDiNCUVoymBPeooqU156d2lnmqAPIf18iDxFjTK60eoyqa5Aa1xN37QFbKDJx3p6StnvQnthWlqT/6gs7Tn0FAHP8tzQZ2h2ZijvbD/2wqTU0ZzHyygitpZTzGdVSC2YUGI3uu6SR5kSXn0k7rU20uYsd+PD4//cMrjPhWpkZDMutWBw==
Received: from VI1EUR04FT033.eop-eur04.prod.protection.outlook.com (2a01:111:e400:7e0e::49) by VI1EUR04HT046.eop-eur04.prod.protection.outlook.com (2a01:111:e400:7e0e::89) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3412.21; Thu, 24 Sep 2020 21:59:25 +0000
Received: from VI1P194MB0285.EURP194.PROD.OUTLOOK.COM (2a01:111:e400:7e0e::51) by VI1EUR04FT033.mail.protection.outlook.com (2a01:111:e400:7e0e::386) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3412.21 via Frontend Transport; Thu, 24 Sep 2020 21:59:25 +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.022; Thu, 24 Sep 2020 21:59:25 +0000
From: Khaled Omar <eng.khaled.omar@outlook.com>
To: Fred Baker <fredbaker.ietf@gmail.com>
CC: Erik Kline <ek.ietf@gmail.com>, "Eric Vyncke (evyncke)" <evyncke=40cisco.com@dmarc.ietf.org>, int-area <int-area@ietf.org>, IPv6 Operations <v6ops@ietf.org>
Thread-Topic: [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)
Thread-Index: AQHWjSq/zPsJZ7YUikO21h6CIi8HxqltUlfwgADfGYCAACCn4IACRiUAgAAC6BCAAc3/gIAAiCMQgAVsNYCAAAKo8A==
Date: Thu, 24 Sep 2020 21:59:25 +0000
Message-ID: <VI1P194MB0285D67301646D4383320B55AE390@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>
In-Reply-To: <601FB9F8-DB83-4654-B652-BE07C49F7918@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-incomingtopheadermarker: OriginalChecksum:9ADCAE4F5AE989F4CD6B538D7A4E0DDAA0F10110BA67C76CD6B1BFA36DAE417F; UpperCasedChecksum:DA6965B6FE4CD29659FE1544EF21C856C2752273866AE85AC8971A237EA51758; SizeAsReceived:7420; Count:44
x-tmn: [hMiQcOnH1iW8tvm9BBNXlYTJOCskpoJb]
x-ms-publictraffictype: Email
x-incomingheadercount: 44
x-eopattributedmessage: 0
x-ms-office365-filtering-correlation-id: c0dd2b83-2865-42fa-43d4-08d860d51a4b
x-ms-traffictypediagnostic: VI1EUR04HT046:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: cT0HQNre/n73oBlrVmeLQXpDLwsrMqUT7zUaeBMP7NRU5hB7HAmm/RwRG8V6pJl7aRdwAq9PpQG2r6c/Z+/dvVymw57R9AoCBIJu4l7UqhZcShjNfQTpFKRcfNS0raLgSAn3GC7D5ChW8ZkiyX1jCDy5fw09n3Acul19D4IiTrYmWHkFIhlkqGt1YBBxta60ddY5AaE/pToR4UMNopIzUBGFcwaOOeQPFL715l6dmYPdLljuk+qVYhRKMMSkSMq7
x-ms-exchange-antispam-messagedata: iAgqd5zmAjheO15DN3HgVBKEvOkZ8st5Kb3wBFNamoq2UsVU59aBVpjz9IBsVAMCxLn9bNuBw0XIQcQCAvU8VFLS8t/fzDR+Q/zmHNVi4a/WOwMLjN5xKqJ7qFYLH19aq0FyVti2AegatCQUtaHArw==
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: VI1EUR04FT033.eop-eur04.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: c0dd2b83-2865-42fa-43d4-08d860d51a4b
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Sep 2020 21:59:25.7776 (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: VI1EUR04HT046
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/HuAMhoN7T7ACnzVuUV6MVaQPhu4>
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)
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: Thu, 24 Sep 2020 21:59:32 -0000

Hi Fred,

That’s a powerful reply from you both, but let me try to check these statistics for 1 week and do some analysis to know whether I can depend on the result without any kind of forcing the end result, and I feel optimistic that the result will be reflecting the real case, I just need some time to be able to go with a conclusion as I have nothing to check out right now.

As you know from the IPv10 I-D, it requires the network between hosts to be IPv4/IPv6 ready, so it still can be considered, as I still think that the movement to IPv6 still need some time and arrangement to get the best result for the coming generations.

So, let me ask Eric if we can reserve a slot in the next meeting to present IPv10.

Thanks,

Khaled Omar

-----Original Message-----
From: Fred Baker <fredbaker.ietf@gmail.com> 
Sent: Thursday, September 24, 2020 11:45 PM
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>; IPv6 Operations <v6ops@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)

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,np,mm,om,bt,kr,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