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

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Wed, 24 November 2021 17:21 UTC

Return-Path: <prvs=1962b87949=jordi.palet@consulintel.es>
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 2A1113A08B8 for <v6ops@ietfa.amsl.com>; Wed, 24 Nov 2021 09:21:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level:
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es
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 vT_vXPii6S9O for <v6ops@ietfa.amsl.com>; Wed, 24 Nov 2021 09:21:34 -0800 (PST)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) by ietfa.amsl.com (Postfix) with ESMTP id B2FED3A08B7 for <v6ops@ietf.org>; Wed, 24 Nov 2021 09:21:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1637774488; x=1638379288; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:Message-ID:Thread-Topic:References:In-Reply-To: Mime-version:Content-type; bh=I3STZi/KxDt7EQPVfWJTEydR9rmnZOAX4m 4TFAiuI9U=; b=oC10nS4Rp525LHXlO+RGgM5nw+NK35QMhJpXzhFti50lwKBbk7 63FlNebJToIik81wGeTDIFlQQmdIpl2TUW/7XTCHXikkUt20DXYd+PSF3Y4xOB9S UjV3R8wFb5c/Qc4DAareunKz/ovKm0S+iF6jijDBNa8y555yNRXx8HRbs=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Wed, 24 Nov 2021 18:21:28 +0100
X-Spam-Processed: mail.consulintel.es, Wed, 24 Nov 2021 18:21:27 +0100
Received: from [10.10.10.145] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50000755735.msg for <v6ops@ietf.org>; Wed, 24 Nov 2021 18:21:27 +0100
X-MDRemoteIP: 2001:470:1f09:495:a848:30e2:73fa:4c9a
X-MDHelo: [10.10.10.145]
X-MDArrival-Date: Wed, 24 Nov 2021 18:21:27 +0100
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1962b87949=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
User-Agent: Microsoft-MacOutlook/16.55.21111400
Date: Wed, 24 Nov 2021 18:21:25 +0100
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "v6ops@ietf.org WG" <v6ops@ietf.org>
Message-ID: <B22F0976-3172-47C4-945B-56F2B9BC0DEE@consulintel.es>
Thread-Topic: [v6ops] Which IPv4aaS mechanisms should CE routers implement first?
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>
In-Reply-To: <CAHL_VyD6GX=5U7yz-d0BQLOqRhpEhGC=Bt=UWmnvh8o2yasyuA@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3720622885_277828972"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Nne4IMOPOTQ_3Wsn6TySoa9aE40>
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:21:39 -0000

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 en nombre de richard@helix.net.nz> escribió:

 

On Wed, 24 Nov 2021 at 14:25, Vasilenko Eduard <vasilenko.eduard=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 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.