This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ipv6-wg] including a CLAT (464XLAT) SSID in RIPE meetings
- Previous message (by thread): [ipv6-wg] New on RIPE Labs: IPv6 Train The Trainer
- Next message (by thread): [ipv6-wg] including a CLAT (464XLAT) SSID in RIPE meetings
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
JORDI PALET MARTINEZ
jordi.palet at consulintel.es
Wed Mar 22 22:54:14 CET 2017
Hi all, I was suggesting the NCC OPS team to include in the meeting network a VM machine that provides a “CLAT” SSID in the meeting network. They suggested that, same as it was done for the NAT64 SSID, the topic is discussed in the IPv6 WG, as there is not a “formal” procedure to agree on that. So, I checked with the IPv6 WG co-chairs and they asked me to foster this topic in the mailing list … so here we are. While 464XLAT has been extensively tested and deployed in the cellular world, I think most of the wireline and wireless (not cellular) ISPs, haven even heard about it or evaluated the potential for those environments, the same that happens probably with MAP-T/E. Having just a NAT64 gives the impression to the people that today you can deploy IPv6-only access to customers and we know is not the case, because the app. Even if 80% (which will take YEARS to happen) of the app developers “correct” their apps, you will still get many things broken in homes and offices. So is undesirable (in my opinion) to work (only) in that direction. And even more, those apps, hardware, etc., that will never be updated, will never work with a NAT64-only scenario. With 464XLAT (or MAP), you avoid deploying CGN, which is a high cost, and you provide the *same* functionality that today “regular” customers (residential, SMEs, even many big companies that don’t have to export IPv4 services outside their LANs). If we demonstrate this “live” in the RIPE meeting network, I think we can change some of the participant’s minds, and I believe the cost of that is really small, may be a couple of hours of one of your OPS team colleagues, as I’ve already done the work and I’m happy to help them on testing in their lab, document what I’ve done (already working on that), and anything else they may need. Also, if the NAT64 is already there, it becomes much easier, as only the VM with the CLAT is needed (unless you want to “separate” the NAT64 for each SSID). By the way, the plan is to have this also in the next meetings of other RIRs (already planned). So, opinions? Regards, Jordi ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.consulintel.es The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
- Previous message (by thread): [ipv6-wg] New on RIPE Labs: IPv6 Train The Trainer
- Next message (by thread): [ipv6-wg] including a CLAT (464XLAT) SSID in RIPE meetings
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]