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

Giuseppe Fioccola <giuseppe.fioccola@huawei.com> Mon, 29 March 2021 09:59 UTC

Return-Path: <giuseppe.fioccola@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 0D1123A36FA for <v6ops@ietfa.amsl.com>; Mon, 29 Mar 2021 02:59:42 -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=unavailable 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 rsMwUNK7IpiH for <v6ops@ietfa.amsl.com>; Mon, 29 Mar 2021 02:59:36 -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 C82933A36FB for <v6ops@ietf.org>; Mon, 29 Mar 2021 02:59:35 -0700 (PDT)
Received: from fraeml713-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4F879f0Wlzz684Nd; Mon, 29 Mar 2021 17:50:30 +0800 (CST)
Received: from fraeml714-chm.china.huawei.com (10.206.15.33) by fraeml713-chm.china.huawei.com (10.206.15.32) 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:59:31 +0200
Received: from fraeml714-chm.china.huawei.com ([10.206.15.33]) by fraeml714-chm.china.huawei.com ([10.206.15.33]) with mapi id 15.01.2106.013; Mon, 29 Mar 2021 11:59:31 +0200
From: Giuseppe Fioccola <giuseppe.fioccola@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+SxeIL8JgufiaKgC+s0iAAKNbSUAAGwGfAAAelwAyAByQ9Gf///G/gIAAClYAgAAWdACAACT+AIAAJzAAgAAEfgCAAAbDAIAADSYAgAAGkoCAARrxAIAEpe88///yVYCAAK3MAIAAGKiA//8kyiCAAbeBAP//20Jg
Date: Mon, 29 Mar 2021 09:59:31 +0000
Message-ID: <167dd02042ad483e956d0c33e59b6e5e@huawei.com>
References: <BL0PR05MB5316425C5650B5D2FE43DE4DAE6C9@BL0PR05MB5316.namprd05.prod.outlook.com> <CAB75xn7=swhtwqRuV6SoWoMO7jtCcPCc02XiVpAjE=VUx8CyaQ@mail.gmail.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> <79F22424-F46F-4E75-AA6C-5CED5C803957@consulintel.es> <92dfb1f9218740c4b385fe52592e329a@huawei.com> <6DBC6ACF-61B7-4500-8ACC-482224DA9DE6@consulintel.es>
In-Reply-To: <6DBC6ACF-61B7-4500-8ACC-482224DA9DE6@consulintel.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.48.210.159]
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/kfig86nhNjraCDbmPPAE-m7Yf4Q>
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:59:42 -0000

Hi Jordi,
Yes, this is exactly my plan.
I will surely use data from the mailing list discussion. I will also try to research public statistics on that, even if, as already noted, it will be very difficult since normally ISPs don't publish this data about their customers.

Regards,

Giuseppe


-----Original Message-----
From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of JORDI PALET MARTINEZ
Sent: Monday, March 29, 2021 11:24 AM
To: v6ops@ietf.org
Subject: Re: [v6ops] draft-vf-v6ops-ipv6-deployment

May be instead of having a "conclusive" description, we should use some of the text and data that we have been exchanging in the last emails?

My inputs are based on real deployment cases. I can't cite specific ones, because customer confidentiality, but also responding to Eduard, yes, there are wireline ISPs that already surpassed 75%. There are both cases where you can apply this % to the total network, and cases where you can apply this % to those customers that already got IPv6 deployed. Again, it depends on the specific ISP strategy (enabling all customers in "n" months, or "overnight" or "in different phases across a multi-year plan").
 
Regards,
Jordi
@jordipalet
 
 

El 29/3/21 9:53, "v6ops en nombre de Giuseppe Fioccola" <v6ops-bounces@ietf.org en nombre de giuseppe.fioccola@huawei.com> escribió:

    Hi,
    Thank you for the inputs about this statement "For this reason, when IPv6 increases to a certain limit, it would be better to switch to the IPv6-only stage."
    I agree that it is not very specific and we should extend the concept in this paragraph.
    We can say that the "limit" can be "when IPv4 traffic is vanishingly small" or "when IPv6 increases to more than 90%", anyway it is difficult to be conclusive since it also depends on several factors.
    As highlighted by Jordi, it should be considered on a case-by-case basis looking at the different strategies of the ISPs and at the different costs involved. 
    We will surely explain and add more considerations on this point in the next revision of the draft.

    Regards,

    Giuseppe

    -----Original Message-----
    From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of JORDI PALET MARTINEZ
    Sent: Sunday, March 28, 2021 10:16 PM
    To: v6ops@ietf.org
    Subject: Re: [v6ops] draft-vf-v6ops-ipv6-deployment


        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.

    -> Yes, agree, I was not trying to say that existing IPv6 deployments (with *any* transition mechanism) should move to IPv6-only with IPv4aaS. My sentence was thinking in "if you deploy IPv6 now".

        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."

    -> Agree. I think it is a case-by-case basis. However, it should be considered that certain customers may need "real" dual-stack (example customer hosting dual-stack contents in their own premises), so one of the reasons may be releasing IPv4 addressers where they aren't longer "absolutely" needed, for other "better" usages, or even because the transfer of IPv4 addresses may cover the cost of moving to IPv6-only. Note also that IPv6-only with IPv4aaS has one more advantage for the ISP: you only manage a single stack, which means less opex, and this impacts more as less IPv4 traffic is there, and you don't need to "disable" IPv4, because it is "automatically" disabled. Instead using "real" dual-stack or older transition mechanisms, means that at some point in the future you may want to do a "new" transition to IPv6-only (which has a cost).



    **********************************************
    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