Re: [v6ops] Which IPv4aaS mechanisms should CE routers implement first?

Xipengxiao <xipengxiao@huawei.com> Wed, 24 November 2021 17:31 UTC

Return-Path: <xipengxiao@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 9E6D53A08CB for <v6ops@ietfa.amsl.com>; Wed, 24 Nov 2021 09:31:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 g6caS9tf7d1K for <v6ops@ietfa.amsl.com>; Wed, 24 Nov 2021 09:31:29 -0800 (PST)
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 AC5FF3A08C3 for <v6ops@ietf.org>; Wed, 24 Nov 2021 09:31:28 -0800 (PST)
Received: from fraeml709-chm.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4HznyB6WLbz67mwQ for <v6ops@ietf.org>; Thu, 25 Nov 2021 01:27:30 +0800 (CST)
Received: from fraeml712-chm.china.huawei.com (10.206.15.61) 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.2308.20; Wed, 24 Nov 2021 18:31:25 +0100
Received: from fraeml712-chm.china.huawei.com ([10.206.15.61]) by fraeml712-chm.china.huawei.com ([10.206.15.61]) with mapi id 15.01.2308.020; Wed, 24 Nov 2021 18:31:25 +0100
From: Xipengxiao <xipengxiao@huawei.com>
To: "v6ops@ietf.org WG" <v6ops@ietf.org>
Thread-Topic: [v6ops] Which IPv4aaS mechanisms should CE routers implement first?
Thread-Index: AQHX4Nq4SLiteVGK1k6GnwpivVm+7awSaJQAgAA9eYCAAAWDgIAAMI4AgAAA04CAABLTIA==
Date: Wed, 24 Nov 2021 17:31:24 +0000
Message-ID: <e8eb66b4894f4162b7e83aa8c8359a93@huawei.com>
References: <CAKD1Yr0z-XckGv5L_9qu5w_6mU=O1h5nZWoTNw6GmStHQ8tzYA@mail.gmail.com> <6f093dad3ed94ddc956f0be5fac6141b@huawei.com> <CAD6AjGRh-REfGXNgxLYMJJHsUFSZq+d10-EqTgMZrnAsbEP+2g@mail.gmail.com> <d5df0d47aa464cb7bcd56192098c32ad@huawei.com> <CAHL_VyD6GX=5U7yz-d0BQLOqRhpEhGC=Bt=UWmnvh8o2yasyuA@mail.gmail.com> <B22F0976-3172-47C4-945B-56F2B9BC0DEE@consulintel.es>
In-Reply-To: <B22F0976-3172-47C4-945B-56F2B9BC0DEE@consulintel.es>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.48.222.192]
Content-Type: multipart/alternative; boundary="_000_e8eb66b4894f4162b7e83aa8c8359a93huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/xiLAasutVr4V8r9VFNAoXjjL4qI>
Subject: Re: [v6ops] Which IPv4aaS mechanisms should CE routers implement first?
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, 24 Nov 2021 17:31:34 -0000

Not sure if my opinion counts, but I support Jordi’s proposal :-)

XiPeng

From: v6ops <v6ops-bounces@ietf.org> On Behalf Of JORDI PALET MARTINEZ
Sent: Wednesday, November 24, 2021 6:21 PM
To: v6ops@ietf.org WG <v6ops@ietf.org>
Subject: Re: [v6ops] Which IPv4aaS mechanisms should CE routers implement first?

Should we make RFC8585 a “must”?

I think is time to take stronger positions from IETF.


El 24/11/21 18:19, "v6ops en nombre de Richard Patterson" <v6ops-bounces@ietf.org<mailto:v6ops-bounces@ietf.org> en nombre de richard@helix.net.nz<mailto:richard@helix.net.nz>> escribió:

On Wed, 24 Nov 2021 at 14:25, Vasilenko Eduard <vasilenko.eduard=40huawei.com@dmarc.ietf.org<mailto:40huawei.com@dmarc.ietf.org>> wrote:
The best MAP use case that I have seen (really rich in technical details) was from Richard Patterson
after Sky did green-field implementation for Italy.
He did it in many please (you could google), I like this version: https://www.ripe.net/participate/meetings/open-house/ripe-ncc-open-house-ipv6-only-networks from 00:37 to 1:09
Ed/


Thanks!

A little update on that, MAP-T is now default-on for all new customers of Sky Italia, and we've migrated about 95% of existing ones.
The stragglers are those with 3rd party CPEs, who we have now proactively sent communications to informing them of their impending migration before the end of the year.  The biggest issue is indeed lack of 3rd party CPE support, their only real other option is OpenWRT currently.

The Italian regulators have a "Modem Libero" policy that prevents operators locking customers into a particular CPE, so it would be great to see additional options become available. (If any CPE vendors want to reach out to me, I'd be happy to help discuss the requirements and offer up some inter-op testing)

-Rich

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