Re: [v6ops] draft-vf-v6ops-ipv6-deployment

Vasilenko Eduard <vasilenko.eduard@huawei.com> Wed, 31 March 2021 16:02 UTC

Return-Path: <vasilenko.eduard@huawei.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 96B9D3A2D0B for <v6ops@ietfa.amsl.com>; Wed, 31 Mar 2021 09:02:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.918
X-Spam-Level:
X-Spam-Status: No, score=-1.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 3a5RwFxJccUn for <v6ops@ietfa.amsl.com>; Wed, 31 Mar 2021 09:01:59 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 829BA3A2CF6 for <v6ops@ietf.org>; Wed, 31 Mar 2021 09:01:57 -0700 (PDT)
Received: from fraeml702-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4F9W6f08lXz685TG for <v6ops@ietf.org>; Wed, 31 Mar 2021 23:52:42 +0800 (CST)
Received: from msceml702-chm.china.huawei.com (10.219.141.160) by fraeml702-chm.china.huawei.com (10.206.15.51) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2106.2; Wed, 31 Mar 2021 18:01:50 +0200
Received: from msceml703-chm.china.huawei.com (10.219.141.161) by msceml702-chm.china.huawei.com (10.219.141.160) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Wed, 31 Mar 2021 19:01:49 +0300
Received: from msceml703-chm.china.huawei.com ([10.219.141.161]) by msceml703-chm.china.huawei.com ([10.219.141.161]) with mapi id 15.01.2106.013; Wed, 31 Mar 2021 19:01:49 +0300
From: Vasilenko Eduard <vasilenko.eduard@huawei.com>
To: JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] draft-vf-v6ops-ipv6-deployment
Thread-Index: AdcZodmxnT/gHUc+SxeIL8JgufiaKgC6gmaAAKGcLoAAHMC6AAAix8rKAByQ6SL//9A5gIAAClYAgAAWdACAACT+AIAAJzAAgAAEfgCAAAbDAIAADSYAgAAGkoCAARrxAIAEx3VS///hkoCAAK3NAIADINEAgAAdfACAAAJ5gIAAn8sA//+81dCAAHB1AP//utVAAAzkBwD//8dmIP//e+oA//65zRA=
Date: Wed, 31 Mar 2021 16:01:49 +0000
Message-ID: <3dc8c969f834493abbbf0172d64fb23e@huawei.com>
References: <BL0PR05MB5316425C5650B5D2FE43DE4DAE6C9@BL0PR05MB5316.namprd05.prod.outlook.com> <6059897e.1c69fb81.ac270.d863SMTPIN_ADDED_BROKEN@mx.google.com> <749643a7-313f-4bd1-8bb8-7dc26d830070@gmail.com> <605aae8f.1c69fb81.8a8ed.04b7SMTPIN_ADDED_BROKEN@mx.google.com> <35c4cf4f-0128-dff6-27a3-4cc868539f7f@gmail.com> <9614BF99-431D-4046-9762-0F111AFBB27D@consulintel.es> <a498117e-4834-41f8-5c90-ad7734d07220@hit.bme.hu> <e770fec1-2189-f683-6c74-36e32541c53d@gmail.com> <abe65114-d9c9-10ee-2c78-449051acbb61@hit.bme.hu> <3c50c72b-b606-a6cf-3095-f08ad48eecf5@gmail.com> <2A0C2B40-2DA4-4941-A09F-5BD31EDA3301@consulintel.es> <2e64b426-3a0a-b5f8-0306-005e9f1023d0@gmail.com> <72754d29-8b57-66fa-2b3a-fc6680c339f2@hit.bme.hu> <69744eb4-2f2e-6876-eba7-c439c5c4db9d@gmail.com> <A9D618FB-00B5-4D87-8D1F-2AE28EF29F62@consulintel.es> <202103281513224517773@chinatelecom.cn> <847EF067-1076-4AC4-9349-2992181119DB@consulintel.es> <43c05777-01c3-df81-9da1-64abd6dc8c91@gmail.com> <0f404c54-c4df-bcf4-bd8b-3aa5e28136fd@otenet.gr> <CABNhwV0OQqAuzo4fpUqCamX8SYuWzYLDDrgjHTQikQP+N28nfg@mail.gmail.com> <6061207C-5226-45D0-AA29-AA133E76F557@consulintel.es> <CABNhwV3HH23NAxNpOGQggviQgEecbVVDiOOCQLR-9kab=MnTVg@mail.gmail.com> <48ebd4f5151040729b39298b4c2d95f9@huawei.com> <2E04A25E-8075-4D94-BFF6-F72B69561BEC@consulintel.es> <282df8e7ea774ef3ae4d7a33fd016b3d@huawei.com> <062AF533-4FE8-4692-87BE-D496A5A58280@consulintel.es> <1883c281565a43f2ae58ceb798943d8d@huawei.com> <FA699995-3BFF-48E7-8E36-C13560D7D677@consulintel.es>
In-Reply-To: <FA699995-3BFF-48E7-8E36-C13560D7D677@consulintel.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.203.100]
Content-Type: multipart/related; boundary="_004_3dc8c969f834493abbbf0172d64fb23ehuaweicom_"; type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/oiEq3ufv2t7Hy_Ay_qpGfg7x9jk>
Subject: Re: [v6ops] draft-vf-v6ops-ipv6-deployment
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: Wed, 31 Mar 2021 16:02:05 -0000

Hi Jordi,
I was probably too pessimistic about the number of cases when CDN proxies from IPv6 to IPv4. I have read that CloudFlare makes it by default (Enterprise could switch off).
I do not believe that man enterprises have incentives to activate this functionality on CDN consciously – they probably do not care. But if it is by default – then they would probably did not touch it too.
It is interesting how many services (%) have been ordered from CDN providers with such proxy activated.
Eduard
From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of JORDI PALET MARTINEZ
Sent: Wednesday, March 31, 2021 6:14 PM
To: v6ops@ietf.org
Subject: Re: [v6ops] draft-vf-v6ops-ipv6-deployment

Hi Eduard,

I’m not sure if I’ve not explained myself about this.

Since many years ago, I will say 100% of the key CDNs/caches are IPv6 enabled. Several of them in fact mandatorily must be IPv6 “connected” (so if an ISP or IX want to host it, must provide IPv6 addresses and connectivity to the CDN/cache). I believe the “mandatory support of IPv6” in order to allow hosting a CDN/Cache is true for Google and Facebook at least, but it is just on top of my head, so my memory could be failing.

Most of them enable IPv6 *by default* unless you manually turn it off, *even if your original content is not* IPv6 enabled.

That means that it is a conscious/deliberated decision to turn off IPv6 in a cache/CDN.

Of course, this decision is often only taken if there is some clear signs of incorrect behavior or impact, for example, because a bad IPv6 deployment inside of an ISP network, and it is disabled “only” towards that ISP, not globally.

There are several colleagues from CDNs in this list, so they can provide further inputs.

However, I did a quick search about the status and defaults of the top ones. Not all the info is clearly presented, but is a matter of digging more in those CDN providers blogs, etc., to find further info.

I’ve not used any specific order in this list, just randomly as they come to my mind:

https://support.cloudflare.com/hc/en-us/articles/229666767-Understanding-and-configuring-Cloudflare-s-IPv6-support

https://www.akamai.com/us/en/multimedia/documents/product-brief/ipv6-adaptation-product-brief.pdf

https://support.google.com/interconnect/answer/9058809?hl=en

https://netflixtechblog.com/enabling-support-for-ipv6-48a495d5196f

https://aws.amazon.com/es/about-aws/whats-new/2016/10/ipv6-support-for-cloudfront-waf-and-s3-transfer-acceleration/

https://www.cachefly.com/cachefly-is-ipv6-compatible/

https://s24.q4cdn.com/538403808/files/doc_news/Limelight-Networks-Automates-IPv6-Enablement-for-New-and-Existing-Customers-2012.pdf

https://techmonitor.ai/technology/networks/tata_communications_launches_global_cdn_service

https://www.codeinwp.com/blog/maxcdn-vs-cloudflare-vs-cloudfront-vs-akamai-edge-vs-fastly/

https://blog.sucuri.net/2016/09/ipv6-adoption.html

https://www.keycdn.com/blog/ipv6-support

https://www.verizondigitalmedia.com/blog/verizon-digital-media-services-announces-ipv6-compliance/

https://www.belugacdn.com/

https://azure.microsoft.com/en-us/updates/ipv6-for-azure-vms/



Saludos,
Jordi
@jordipalet



El 31/3/21 13:11, "v6ops en nombre de Vasilenko Eduard" <v6ops-bounces@ietf.org<mailto:v6ops-bounces@ietf.org> en nombre de vasilenko.eduard@huawei.com<mailto:vasilenko.eduard@huawei.com>> escribió:

Hi Jordi,
The fact that something is going to CDN would not help you. Because every CDN accelerates many Web sites.
If the original Web site does not support it – then CDN could not help here. It would continue to stream IPv4 for this request.
For your question: “how much traffic could be IPv6 overnight” – we need traffic per primary N Web sites.
Sorry, the cheapest is cFlowd statistics for this. DPI is more expensive.
Eduard
From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of JORDI PALET MARTINEZ
Sent: Wednesday, March 31, 2021 1:44 PM
To: v6ops@ietf.org<mailto:v6ops@ietf.org>
Subject: Re: [v6ops] draft-vf-v6ops-ipv6-deployment

Hi Eduard,

All the customers I’ve worked with, even just for trainings, and also operators that participated in “free/open trainings” for example in RIR and NOG meetings, have answered this question “do you know how much % of your traffic goes to CDNs/caches”? I’m talking about over 75.000 engineers that I’ve trained since 2001, and I started asking this question around 2010, so let’s say in the worst case only 1/3rd of them know the answer (because I did less trainings in the last 10 years than the first 10 ones).

I guess this is something they can measure at the edge of the border, peerings, etc., etc. I don’t really care how they do it, if it is fairly close to reallity, otherwise, they will haven’t answered so categorically. For example, they know how much traffic goes to the self-hosted CDNs/caches or IX, in case they don’t host their own CDNs/caches but the IXs offers them, etc.

The response has been initially “more than 65%”, then I started to get answers closer to 75%, 80-90%. I didn’t took note one by one to make my own “stats”, but when I consintently get an answer over 65% and I notice that, across the years that this response is going higher and higher, I think we can have some conclusions and not be too much erred.

We don’t need to “check” if the destination is IPv6 ready. Today, it will be dificult to believe that *any* CDN/cache is not IPv6-ready. We should not count if CDN “x” has disabled IPv6 for customer “y”, because that means “that” customer is not yet IPv6-enabled or they did a bad deployment and the CDN decided to turn it off to avoid issues.

What we pretend to measure is “if you do a good IPv6 deployment in all your customers (at least in the residential ones) how much traffic will use the CDNs/caches with IPv6”. Just knowing how much IPv4 traffic today is going to the same CDNs/caches, provides a very good anser to that question.

Regards,
Jordi
@jordipalet



El 31/3/21 12:22, "v6ops en nombre de Vasilenko Eduard" <v6ops-bounces@ietf.org<mailto:v6ops-bounces@ietf.org> en nombre de vasilenko.eduard@huawei.com<mailto:vasilenko.eduard@huawei.com>> escribió:

Hi Jordi,
When I was on the big Carrier side
We have collected cFlowd sampled statistics (for many reasons).
Then it was possible to put it into some database
And then get N biggest traffic directions out of it.
It was a pure manual exercise in our case.
The result has given many surprises to us☺

The next option is to use DPI statistics that could be of the same rich. DPI (PCEF) is available only on Mobile.
I am not sure they have a pre-loaded template, but chances are good. Just one problem: the discussion below was more about FBB, not MBB.

Unfortunately, all off-line traffic engineering tools (I would not mention 3 vendor’s names here) collect statistics only for MPLS LSPs. That would not help here.
One other big tool has a big collection of sampled cFlowd but it refuses to let it out of a proprietary database.
Hence, such statistics could not be collected for free in any other process or tool.
It is a specialized “project”.

I am not sure that many Carriers could do what you want. This task was not easy a few years ago.
Staring from the fact that not all carriers collect sampled cFlowd from all ports to general-purpose collector, then facing the problem to aggregate it.

Additionally, they need some check which one destination is IPv6 ready. It would be a manual process too.
Eduard
From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of JORDI PALET MARTINEZ
Sent: Wednesday, March 31, 2021 11:42 AM
To: v6ops@ietf.org<mailto:v6ops@ietf.org>
Subject: Re: [v6ops] draft-vf-v6ops-ipv6-deployment

And more important than that … this site only shows “number” of websites, but it doesn’t show “how” much % of traffic those web sites are delivering vs. % worldwide.

This is very simple. We can make a poll and evaluate the results in the list. We can find a way to make it anonymous (no need to indicate your email or name). People could respond the poll without telling what is the ASN/network, just be honest when responding. What do you think Fred/Ron?

Each operator or people having details of one or more networks, to tell us how much traffic in your network is going to caches and CDNs, you don’t need to indicate which ones, just totals (so include all the big ones such as video services, social networks, or other well-know that have IPv6-enabled).

It doesn’t matter if you don’t offer IPv6 to your customers. If you know that (for example), 85% of your traffic is towards those services, we know that turning IPv6 on to your customers will turn your % of IPv6 traffic towards that figure.

Even if we ignore “smaller” sites, the % of traffic to them is probably negligible, even if an “important” service for an specific operator is not there. This can compensate somehow the % of IPv4 traffic to video sources from older (non-IPv6 enabled) smartTVs or STBs.

Regards,
Jordi
@jordipalet



El 31/3/21 9:03, "Vasilenko Eduard" <vasilenko.eduard@huawei.com<mailto:vasilenko.eduard@huawei.com>> escribió:

Just small good news:
Content is not “sitting steady at 15% IPv6”.
It has healthy 23% CAGR by https://w3techs.com/technologies/history_overview/site_element/all
[cid:image001.png@01D7265F.80AB0840]
Chicken and egg are evolving one after another.
Eduard
From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Gyan Mishra
Sent: Wednesday, March 31, 2021 9:00 AM
To: JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org<mailto:jordi.palet=40consulintel.es@dmarc.ietf.org>>
Cc: v6ops@ietf.org<mailto:v6ops@ietf.org>
Subject: Re: [v6ops] draft-vf-v6ops-ipv6-deployment


In theory if you flipped a switch and all fixed broadband and wireless 4G/5G access layer providers all around the world banded together and ditched CGN and turned up IPv4AAS and so now all subscribers - all the billions of subscribers around the world are now officially IPv6 only.

However let’s say this happened tomorrow but our web content and traffic volume is still sitting steady at 15% IPv6 and 85% IPv4.

The needle would not have moved at all as we only fixed half the problem.

We need to get all the web content to move to IPv6 and that’s an problem of economics that we need to push the envelope on all web content providers charge high for IPv4 premium $$ to incentivize moving to IPv6 by forces of economy where money talks.

Gyan

On Tue, Mar 30, 2021 at 4:29 PM JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org<mailto:40consulintel.es@dmarc.ietf.org>> wrote:
I will say that the “long” and “unpredictable” time for IPv4aaS is an advantage, because you “stop” provisioning IPv4 now, so it is one less problem to worry about.
You’re not longer worried about “how” much usage of IPv4 is done, except for a single thing: reducing the number of IPv4 addresses in the NAT64 (for example in the case of 464XLAT). You could even ignore that, but of course, it is good to reduce the number of IPv4 addresses if they are not used, because you can either transfer them and get some money back or use in other parts of the network.
The question is: Do you prefer to ged rid off IPv4 as in many parts of the network as possible sooner or later?


El 30/3/21 22:21, "v6ops en nombre de Gyan Mishra" <v6ops-bounces@ietf.org<mailto:v6ops-bounces@ietf.org> en nombre de hayabusagsm@gmail.com<mailto:hayabusagsm@gmail.com>> escribió:



On Tue, Mar 30, 2021 at 2:34 PM Yannis Nikolopoulos <yanodd@otenet.gr<mailto:yanodd@otenet.gr>> wrote:


On 3/28/21 9:47 PM, Brian E Carpenter wrote:
> Dual stack has no time limit
(for us ISPs) it has, it painfully has, if your user base is still growing

Gyan> I think to your POV there is a flip side as dual stack is simple and easy cannot get any simpler than that, however the downside is the process of deployment can be painfully slow but it all depends. If you are provisioning 1000s of sites for dual stack that still can be done with ZTP even with complex DMVPN or other overlay topologies dual stacked still not difficult.  I think whenever manual configuration comes into play and you have even a 100 sites or devices that can be painful and lengthy process.

There are definite tradeoffs.

Dual stack is less complexity but then you have IPv4  provisioning and numbering plan so you could say that in itself is complex.

If it’s fixed broadband BNG or 4G/5G mobile the drawback as well with dual stack is IPv4 addressing numbering plan but having to maintain configuration for both IPv4 and IPv6 could be considered complex, even though the dual stack process is as simple as it gets.

With IPv4 AAS the attraction could be the minimum configuration footprint number of lines of config.

Learning curve yes for operators but you could say that for any technology their is a learning curve.

I think the bigger deal for operators is how long the timeframe to maintain IPv4AAS is a bigger factor as that could be decades and it could be almost like a permanent solution.




_______________________________________________
v6ops mailing list
v6ops@ietf.org<mailto:v6ops@ietf.org>
https://www.ietf.org/mailman/listinfo/v6ops
--

[http://ss7.vzw.com/is/image/VerizonWireless/vz-logo-email]<http://www.verizon.com/>

Gyan Mishra

Network Solutions Architect

Email gyan.s.mishra@verizon.com<mailto:gyan.s.mishra@verizon.com>

M 301 502-1347

_______________________________________________ v6ops mailing list v6ops@ietf.org<mailto:v6ops@ietf.org> https://www.ietf.org/mailman/listinfo/v6ops

**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
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.
_______________________________________________
v6ops mailing list
v6ops@ietf.org<mailto:v6ops@ietf.org>
https://www.ietf.org/mailman/listinfo/v6ops
--

[http://ss7.vzw.com/is/image/VerizonWireless/vz-logo-email]<http://www.verizon.com/>

Gyan Mishra

Network Solutions Architect

Email gyan.s.mishra@verizon.com<mailto:gyan.s.mishra@verizon.com>

M 301 502-1347


**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
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.
_______________________________________________ v6ops mailing list v6ops@ietf.org<mailto:v6ops@ietf.org> https://www.ietf.org/mailman/listinfo/v6ops

**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
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.
_______________________________________________ v6ops mailing list v6ops@ietf.org<mailto:v6ops@ietf.org> https://www.ietf.org/mailman/listinfo/v6ops

**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
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.