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)

Fred Baker <fredbaker.ietf@gmail.com> Thu, 24 September 2020 21:45 UTC

Return-Path: <fredbaker.ietf@gmail.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 940B23A12EC; Thu, 24 Sep 2020 14:45:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, SPF_HELO_NONE=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=gmail.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 XWNwk8EBcXXe; Thu, 24 Sep 2020 14:45:31 -0700 (PDT)
Received: from mail-pf1-x42d.google.com (mail-pf1-x42d.google.com [IPv6:2607:f8b0:4864:20::42d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBD653A14F9; Thu, 24 Sep 2020 14:44:43 -0700 (PDT)
Received: by mail-pf1-x42d.google.com with SMTP id k8so844583pfk.2; Thu, 24 Sep 2020 14:44:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=oE46GT2uISE3K858puf8QXc/hfhON+gT82NPpJVmzxo=; b=n5NicfTvwDLvqZ9UQwUVeMgWBikYdZqqOy3ZUOcG+sI21RZTK2f+ttAtDByP5H/zGX hYxUYf3bgZEDNEtJ8fmEk4mcxw8SItOMI7lyUlxx+vXhXtAMb4efVyx5J5iJkk5pL+r8 kLhCBfV4t8nHuW+jQR7p2qKhKqninvK2TH56nma5KgeEvLPrfFrjl8bC7jM1cPa484PA wbjqYGXCMZ4u9AgcRJa2hssYBv5Hkl8UrM9UNrkgXkD7Y58PHHu+FeoOFsB/IwINAJVC oY/9nyDcAD5HTJF/+2Dsqs8ddexQwg9WDxShtOmw02zKToF7Zxt3Iw8U7lE7pRobppAF l8AA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=oE46GT2uISE3K858puf8QXc/hfhON+gT82NPpJVmzxo=; b=g9CpLnnQjT/pcRdcdB0kBoc79gqddL2xRq7tFI/JwARS/8P7OgRBFlgAz4OVRGNuWV 4oiX7hAh+Dd9I4RxYgn97VP7ZpykiAycdHMe1i8Rj6QDtswdIMl5k0BLQyZAPlerARJ2 vM2CxqIhCC1SOD4yPPYAardTztETQE6gIZQbMrYxGOHF/8GG7WdtHqJBghb5GDF+sBmR GJ0Zb/tsm5Gm9fKARX65WhVGXUQSdeaMML+PrV3GH5iqqLM9tcqJ73KOlEWMYfEKmQYb ueFaZ6+obutaJZr/2IIEFTOLsU2WVflbVSFP1CD+PdM2vfm0YJrHyMqzLuUK+6Q0ryfA EGUw==
X-Gm-Message-State: AOAM5302/1xd6d/JOKYHCpM4s1s5zW8j8jiu0JT84OQW8SGUmu1JZxd5 yC+NlNYcMiUyHXeTIyGIAco=
X-Google-Smtp-Source: ABdhPJybaGGc6eNaThoyQ79PGc/VCz5Ty/417ewbn9EX1DJvpKLwOo7vmx7OwjL0sWmJi7mu6LWvnA==
X-Received: by 2002:a17:902:fe0b:b029:d1:9bd3:6e20 with SMTP id g11-20020a170902fe0bb02900d19bd36e20mr1143748plj.31.1600983883144; Thu, 24 Sep 2020 14:44:43 -0700 (PDT)
Received: from localhost.localdomain (ip68-111-231-227.sd.sd.cox.net. [68.111.231.227]) by smtp.gmail.com with ESMTPSA id h15sm397491pfo.194.2020.09.24.14.44.41 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 24 Sep 2020 14:44:42 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.0.3.2.33\))
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <VI1P194MB0285B8AE9ACE88D1AF051ADAAE3A0@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM>
Date: Thu, 24 Sep 2020 14:44:41 -0700
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>
Content-Transfer-Encoding: quoted-printable
Message-Id: <601FB9F8-DB83-4654-B652-BE07C49F7918@gmail.com>
References: <VI1P194MB0285F47132384AC7C0D8A8DCAE3C0@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM> <F2516A37-06B1-44FC-850F-307114B7D6A5@gmail.com> <VI1P194MB0285B8AE9ACE88D1AF051ADAAE3A0@VI1P194MB0285.EURP194.PROD.OUTLOOK.COM>
To: Khaled Omar <eng.khaled.omar@outlook.com>
X-Mailer: Apple Mail (2.3654.0.3.2.33)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/e7m58X3Q6UBvNW3AJViRCvXO-Nw>
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)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 24 Sep 2020 21:45:34 -0000

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