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

Vasilenko Eduard <vasilenko.eduard@huawei.com> Mon, 29 March 2021 09:36 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 61C8C3A3667 for <v6ops@ietfa.amsl.com>; Mon, 29 Mar 2021 02:36:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 NoHrLsZHKKBg for <v6ops@ietfa.amsl.com>; Mon, 29 Mar 2021 02:36:23 -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 D281C3A366E for <v6ops@ietf.org>; Mon, 29 Mar 2021 02:36:18 -0700 (PDT)
Received: from fraeml709-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4F86lb4frjz6850S for <v6ops@ietf.org>; Mon, 29 Mar 2021 17:31:23 +0800 (CST)
Received: from msceml701-chm.china.huawei.com (10.219.141.159) by fraeml709-chm.china.huawei.com (10.206.15.37) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Mon, 29 Mar 2021 11:36:15 +0200
Received: from msceml703-chm.china.huawei.com (10.219.141.161) by msceml701-chm.china.huawei.com (10.219.141.159) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Mon, 29 Mar 2021 12:36:15 +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; Mon, 29 Mar 2021 12:36:15 +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///hkoCAAK3NAIAAClCAgAAPY4D//xO1MIABxiuA///Kp7A=
Date: Mon, 29 Mar 2021 09:36:15 +0000
Message-ID: <5de63c2346ce45fbb6c534996f794aec@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> <683bf6ac-261e-e492-935d-27d5b1051521@hit.bme.hu> <8D04AA80-A140-4D9D-84AF-35D4206A7C55@consulintel.es> <d38cc2317f8f4ec0b3e2a59bc9905e87@huawei.com> <231084C0-CAE4-4754-B4B0-75C8A1A82D54@consulintel.es>
In-Reply-To: <231084C0-CAE4-4754-B4B0-75C8A1A82D54@consulintel.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.195.151]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/1EwiyisSO3n86A50Zi19YZJHj0o>
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: Mon, 29 Mar 2021 09:36:27 -0000

Hi Jordi,
IMHO: % of IPv6 traffic from IPv6-capable devices are interesting too.
It could be 90%+ with some IPv4aaS service.

But it is not the replacement of overall IPv6 traffic that is needed too. This number is more important for Carrier.
Eduard
-----Original Message-----
From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of JORDI PALET MARTINEZ
Sent: Monday, March 29, 2021 12:20 PM
To: v6ops@ietf.org
Subject: Re: [v6ops] draft-vf-v6ops-ipv6-deployment

HI Eduard,

Life is not so easy!

Even in a cellular network, you may still have an interesting % of users with old phones, even not "smartphones", they may be only 2.5G, etc. This is something key when you work in countries "less developed". This is one of the first parts of the analysis that we do for every customer, questions such as how many phones support IPv6? How many are iOS vs Android vs Windows (others typically are meaningless)? How much time typically take users to get a "new" phone? Are those "new" phones not really new but 2nd hand (so may be still not supporting IPv6)?, etc., etc.

So clearly if you know, for example, that 20% of your customers have outated or non-IPv6 phones, you will not be able to reach more than 80%.

In the case of residential (wireline) services, some users may have replaced the router, and it may not be IPv6-capable (according to the ISP offering), so they need to keep it dual-stack or just IPv4.

Also, some times (both in cellular and wireline), you don't do the IPv6 turn-on in the complete network in a single stage, you may do it per regions, or depending on users contracts, UE capabilities, etc., etc. It is very common an approach such as: New customers get IPv6-only with IPv4aaS + customers with replaced CPEs (failure of the CPE, moving from DSL to GPON, moving to a new location, etc.); then you plan for new service offerings that require a CPE replacement (example triple play, higher bandwidh, better WiFi coverage, 1Gig ports instead of fast ethernet, etc.) - in this case it may mean "customer needs to pay an small extra fee"; then you may want to enforce the replacement of the rest per regions, etc.

By the way, the 4 big mobile carriers in US are already over the 90%. This is reported by ISOC stats, based on measurements.

When I say overnight, I actually should explain it better, and explain that this % is from the users where you enable IPv6-only with IPv4aaS, otherwise, if you still have a % of users that still have older CPEs or UEs, it can't be true.

And yes, agree ... probably the figure is closer to 90% than 75%, at least in the case of mobile providers in stronger economies, which tend to have a faster "update" rate of smartphones.



El 29/3/21 9:33, "v6ops en nombre de Vasilenko Eduard" <v6ops-bounces@ietf.org en nombre de vasilenko.eduard@huawei.com> escribió:

    Hi Jordi,
    Your last statement is probably too strong.
    About half of Mobile carriers have 464XLAT, but only a couple of them reached 90%+.
    If one would think logically about this fact then one would conclude that 90% is not easy to reach, not overnight.
    I have seen in some RFC (do not remember the number) that 75% is easy to reach (it was supported by numbers), but it was a few years ago - this data should be better now because we have 20%+ CAGR for Webservers IPv6 support.
    Hence, the truth is probably somewhere between 75% and 90%.
    Eduard
    -----Original Message-----
    From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of JORDI PALET MARTINEZ
    Sent: Sunday, March 28, 2021 11:20 PM
    To: v6ops@ietf.org
    Subject: Re: [v6ops] draft-vf-v6ops-ipv6-deployment

    I can confirm that ... just say it in my previous email ...

    Note also that for residential ISPs, reaching IPv6 levels close to 90% is trivial. It happens overnight, because the big volume of traffic to CDNs such as Netflix, Youtube/Google, Facebook, Akamai, etc., etc. which have already IPv6 on.




    El 28/3/21 21:25, "v6ops en nombre de Lencse Gábor" <v6ops-bounces@ietf.org en nombre de lencse@hit.bme.hu> escribió:

        However, a statement like:

        "For this reason, when IPv4 traffic is vanishingly small (e.g. less than 1%), it would be better to switch to the IPv6-only stage."

        seems to be trivial.

        Can we state something stronger?

        For example:

        "For this reason, when IPv6 increases to a certain limit (e.g. more than 90%), it would be better to switch to the IPv6-only stage."

        Rationale:
        - Introducing an IPv4aaS technology has its costs, but the selling of 
        the lions share of the public IPv4 addresses brings in more money.
        - The maintenance cost of the IPv4aaS solution is less than that of a 
        complete IPv4 network.

        I do not state that it is true, I just ask, if it can be true. Because 
        if it is so, then it could be a better guidance.

        Gábor

        28/03/2021 20:47 keltezéssel, Brian E Carpenter írta:
        > On 28-Mar-21 21:25, JORDI PALET MARTINEZ wrote:
        >> Yes and not … IPv6 in IPv4 (6in4, proto41, etc.) … 6over4 is another protocol.
        >>
        >>   
        >>
        >> Agree, right thing is to use IPv6-only and IPv4aaS, I was just saying that Free was the initiation of 6RD and they were using that. I’m not saying they still use the same or they should keep using the same.
        > But please consider that if an operator is already supporting its customers using classical dual stack or a solid solution like 6rd, there may be no good reason to change for the next ten years or more. Dual stack has no time limit.
        >
        > I think this statement in the draft:
        > "For this reason, when IPv6 increases to a certain limit,
        > it would be better to switch to the IPv6-only stage."
        > is too vague to be useful. Switching costs might be very high, including loss of customers. In fact, the criterion for switching might be as simple as "when IPv4 traffic is vanishingly small."
        >
        >     Brian
        >
        >
        >
        >>   
        >>
        >> Regards,
        >>
        >> Jordi
        >>
        >> @jordipalet
        >>
        >>   
        >>
        >>   
        >>
        >>   
        >>
        >> El 28/3/21 9:14, "v6ops en nombre de xiechf@chinatelecom.cn <mailto:xiechf@chinatelecom.cn>" <v6ops-bounces@ietf.org <mailto:v6ops-bounces@ietf.org> en nombre de xiechf@chinatelecom.cn <mailto:xiechf@chinatelecom.cn>> escribió:
        >>
        >>   
        >>
        >>   
        >>
        >>   
        >>
        >> 6rd is a mode of IPv6 over IPv4, it is opposite to the concept of "IPv4 as a Service" of IPv6-only, so it should be replaced to make IPv6 as a univeral and underlying network protocol gradually.
        >>
        >>   
        >>
        >> Regards
        >>
        >> Chongfeng
        >>
        >>   
        >>
        >>   
        >>
        >>      *From:* JORDI PALET MARTINEZ <mailto:jordi.palet=40consulintel.es@dmarc.ietf.org>
        >>
        >>      *Date:* 2021-03-25 17:15
        >>
        >>      *To:* v6ops@ietf.org <mailto:v6ops@ietf.org>
        >>
        >>      *Subject:* Re: [v6ops] draft-vf-v6ops-ipv6-deployment
        >>
        >>      Free was using 6RD initially, not sure if they turned into dual-stack, may be with IPv4 via CGN.
        >>
        >>       
        >>
        >>      Regards,
        >>
        >>      Jordi
        >>
        >>      @jordipalet
        >>
        >>       
        >>
        >>      El 24/3/21 17:23, "v6ops en nombre de Alexandre Petrescu" <v6ops-bounces@ietf.org en nombre de alexandre.petrescu@gmail.com> escribió:
        >>
        >>       
        >>
        >>       
        >>
        >>       
        >>
        >>          Le 24/03/2021 à 16:59, Gabor LENCSE a écrit :
        >>
        >>          > Dear Alex,
        >>
        >>          >
        >>
        >>          > On 3/24/2021 4:12 PM, Alexandre Petrescu wrote: [...]
        >>
        >>          >> Does IPv6 mandate the use of DNS64 and NAT64?
        >>
        >>          >
        >>
        >>          > Of course, not. :)
        >>
        >>       
        >>
        >>          So I agree with you about that.
        >>
        >>       
        >>
        >>          > There are several IPv4 as a Services solutions exist. We have
        >>
        >>          > covered the five most prominent ones 464XLAT, DS-Lite, MAP-E, MAP-T
        >>
        >>          > and lw4o6 in our I-D:
        >>
        >>          > https://tools.ietf.org/html/draft-lmhp-v6ops-transition-comparison-06
        >>
        >>          > > Your ISP is likely using one of them.
        >>
        >>       
        >>
        >>          For clarification - my ISP is called 'Free' (it has freedom features).
        >>
        >>       
        >>
        >>          They offer me paid IPv4 and IPv6 native access at home on ADSL.  It's
        >>
        >>          one publicly routable IPv4 address and an IPv6 /56 prefix globally
        >>
        >>          routable prefix (a 'GUP' if I can say so, not a GUA'(ddress)).
        >>
        >>       
        >>
        >>          Up to now, looking through the configuration interface of my freebox at
        >>
        >>          home I could not see the options that you mention (464XLAT, DSLITE,
        >>
        >>          MAP-E, MAP-T, lw4o6).  One might say that they are there invisible, but
        >>
        >>          I doubt that, I need a proof of it.  How can I check for presence of
        >>
        >>          options 464XLAT, DSLITE, MAP-E, MAP-T or lw4o6?
        >>
        >>       
        >>
        >>          The problems that appear when I try to browse IPv6 sites that absolutely
        >>
        >>          need IPv4 might be because I turned off the IPv4 stack on my computer's
        >>
        >>          interface (Windows Properties on the Interface, check off IPv4).  This
        >>
        >>          operation (turning off IPv4 in a computer) is possible only on Windows,
        >>
        >>          not on linux, AFAIR.  One cant do 'rmmod ipv4' in linux.
        >>
        >>       
        >>
        >>          That also explains the fact that installing IPv4-IPv6 translation boxes
        >>
        >>          (NAT64, 464LAT, etc.) in a network is not sufficient to access IPv4
        >>
        >>          sites from an IPv6-only computer.
        >>
        >>       
        >>
        >>          In order to access IPv4 sites from IPv6-only computers one also needs
        >>
        >>          the IPv4 stack to work ok on that computer and, moreover, it needs some
        >>
        >>          times software features in the Client that support the 64:: notation of
        >>
        >>          IPv6 addresses.  For example, thunderbird (a very modern MUA) does not
        >>
        >>          understand it and gets confused by it.  It takes it for an fqdn, and
        >>
        >>          does not even try to connect the translation boxes.
        >>
        >>       
        >>
        >>          This means that if one wants to migrate more to IPv6 then one has to
        >>
        >>          think about the NAT64 and 464XLAT concepts more outside of the cellular
        >>
        >>          network concept.
        >>
        >>       
        >>
        >>          And yes, I agree with you, NAT64 and 464XLAT are good tools to
        >>
        >>          migrate.  In particular, if one is on a smartphone or other computer
        >>
        >>          using an OS that cant turn off their IPv4 stacks.
        >>
        >>       
        >>
        >>          Alex
        >>
        >>       
        >>
        >>          >
        >>
        >>          > Best regards,
        >>
        >>          >
        >>
        >>          > Gábor
        >>
        >>          >
        >>
        >>          > _______________________________________________ v6ops mailing list
        >>
        >>          > v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
        >>
        >>       
        >>
        >>          _______________________________________________
        >>
        >>          v6ops mailing list
        >>
        >>          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
        >>
        >>      https://www.ietf.org/mailman/listinfo/v6ops
        >>
        >> _______________________________________________ v6ops mailing list 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
        >> https://www.ietf.org/mailman/listinfo/v6ops
        >>
        > _______________________________________________
        > v6ops mailing list
        > v6ops@ietf.org
        > https://www.ietf.org/mailman/listinfo/v6ops
        >

        _______________________________________________
        v6ops mailing list
        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
    https://www.ietf.org/mailman/listinfo/v6ops
    _______________________________________________
    v6ops mailing list
    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
https://www.ietf.org/mailman/listinfo/v6ops