[AfrIPv6-Discuss] Finding solutions to things that stop people moving to IPv6

Sat Dec 1 13:29:09 UTC 2018

For the CPEs you may want to ask your vendors to support this document:

https://datatracker.ietf.org/doc/draft-ietf-v6ops-transition-ipv4aas/

Yesterday night was sent to the IESG for the final review, and hopefully will be an RFC in the coming weeks.

In terms of transition, if you have a cellular network, or want to make sure to be "compatible" with it in the future, I will suggest using 464XLAT.

You have also this document as guidelines for deploying it:

https://datatracker.ietf.org/doc/draft-ietf-v6ops-nat64-deployment/

Regards,
Jordi

-----Mensaje original-----
De: Willy MANGA <mangawilly at gmail.com>
Responder a: IPv6 in Africa Discussions <afripv6-discuss at afrinic.net>
Fecha: sábado, 1 de diciembre de 2018, 12:52
Para: "afripv6-discuss at afrinic.net" <afripv6-discuss at afrinic.net>
Asunto: [AfrIPv6-Discuss] Finding solutions to things that stop people moving to IPv6

    Hi,
    I pick it from rpd list [1] because I do not think it's the right place
    to discuss it ... I'll appreciate if people can express share their
    opinions on points below and eventually share their experiences.

    1. https://lists.afrinic.net/pipermail/rpd/2018/008662.html

    Le 01/12/2018 à 07:16, Andrew Alston a écrit :
    > You know,
    > [...]
    > Now let me talk about IPv6 – something I happen to know a fair bit about – particularly in terms of ISP deployments.  Let us be completely honest, IPv6 is necessary – and we all have to get there – it’s not an option – v4 simply doesn’t scale to global needs.  But – instead of these meaningless platitudes about how everyone should go to IPv6 – how about we start openly and honestly talking about the challenges with IPv6 and how we address them – so that we can promote its deployment through proper understanding – and instead of everyone going “lets all move to ipv6” – let’s start finding solutions to some of the things that STOP people moving to IPv6.
    > 
    > 
    >   1.  Lack of legacy support in a fair ton of hardware – how do we deal with it
    >   2.  Vastly inconsistent support for transition mechanisms and chronically bad support for most of these transition mechanisms in CPE’s
    >   3.  The complete *mess* that MPLS support as concerns IPv6 (to this day you cannot do vpnv6 without a v4 underlay, martini is entirely bound to LDP and LDPv6 support is near non-existent, and I’ve yet to see Kompella working entirely without v4 in some form either)
    >   4.  The security challenges around IPv6 and the bad implementations that create issues here – issues which over the years we have learnt to deal with in IPv4 – Happy to expound on these off list – and no – they have nothing to do with NAT or the lack thereof – because NAT as a security mechanism was the biggest lie ever sold to an industry.
    > 
    > For years I have been an IPv6 advocate – and I still am – and I’ve actively deployed and run IPv6 in production supplying it to the end user, with multiple percentage point changes in country IPv6 penetration statistics as a result, but I am fast realizing that if we want IPv6 to grow and thrive – it’s time we started being a little more open and honest about the challenges and problems with it – instead of sprouting off that everyone should just move to it.   Let’s acknowledge that IPv6 is critical, we have no option, but it is also deeply flawed, has major problems, and until start dealing with those – we will see deployment continue to stutter
    > 
    > Andrew

    -- 
    Willy Manga
    @ongolaboy
    https://ongola.blogspot.com/

    _______________________________________________
    AfrIPv6-Discuss mailing list
    AfrIPv6-Discuss at afrinic.net
    https://lists.afrinic.net/mailman/listinfo/afripv6-discuss

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