<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 3/15/19 6:30 AM, Akinremi Peter
      Taiwo wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAGK4d0_kv8gJHgRU_HUyn__HGjELCmLEDqCKqFxXHBDxK209Ew@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div dir="ltr">Good recommendations Toyin. </div>
        <div dir="ltr"><br>
          <div>
            <div>IPv6 discussions should accommodate both the policy,
              infrastructure, technical skills to the business side.
              What I have learnt in project governance is that there
              must be buying of the management to setting a framework
              for successful implementation. </div>
            <div>In my view, regulators need to have a total buying of
              the adoption of IPv6 to setting a workable framework that
              can lead to a successful implementation of IPv6 in Africa.
              <br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <p>I did some research years ago into what government policies had
      worked (or not worked) for promoting IPv6 deployment in a country,
      and what else worked. I found that governments were most effective
      when they had purchasing requirements that whatever product or
      service they bought must use IPv6. That one policy meant that some
      government worker had to work with local ISP(s) and local web
      host(s) to get IPv6. In a competitive market, it's very helpful
      for the government to say, "The ISP who can provide IPv6 first
      will win all of the government's Internet access business. The web
      hosting company who can provide IPv6 will win all of the
      government's hosting business."  The nice thing is that the web
      hosting company is then also pushing the ISP.</p>
    <p>Once this happens, the next time somebody asks the ISP or web
      host for IPv6, they can say yes.</p>
    <p>On a related note, I have seen some countries whose government
      web sites are hosted outside the country. A simple policy that
      government web sites must be hosted in country, on IPv6, will
      provide better service to citizens by making the web faster.<br>
    </p>
    <blockquote type="cite"
cite="mid:CAGK4d0_kv8gJHgRU_HUyn__HGjELCmLEDqCKqFxXHBDxK209Ew@mail.gmail.com">
      <div dir="ltr">
        <div dir="ltr">
          <div>
            <div><br>
            </div>
            <div>Also, the IPv6 conversation must well articulate the
              business side as the main stakeholder are business
              oriented. Some of the questions would be;</div>
          </div>
        </div>
      </div>
    </blockquote>
    These are excellent questions!  <br>
    <blockquote type="cite"
cite="mid:CAGK4d0_kv8gJHgRU_HUyn__HGjELCmLEDqCKqFxXHBDxK209Ew@mail.gmail.com">
      <div dir="ltr">
        <div dir="ltr">
          <div>
            <div>
              <ul>
                <li>Would adoption of IPv6 lead to more coverage and
                  profit digit addition? <br>
                </li>
              </ul>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    With the above government policies, yes! Also, as I said in an
    earlier email, if your service is faster than your competitor, you
    may be able to win more profit.<br>
    <blockquote type="cite"
cite="mid:CAGK4d0_kv8gJHgRU_HUyn__HGjELCmLEDqCKqFxXHBDxK209Ew@mail.gmail.com">
      <div dir="ltr">
        <div dir="ltr">
          <div>
            <div>
              <ul>
                <li>What is the cost and organizational capacity for its
                  deployment?</li>
              </ul>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    There is rarely significant capital cost. It's pretty much all
    labor: the work of learning IPv6, and updating the provisioning and
    monitoring systems, and of testing and configuring the routers and
    firewalls and servers. <br>
    <blockquote type="cite"
cite="mid:CAGK4d0_kv8gJHgRU_HUyn__HGjELCmLEDqCKqFxXHBDxK209Ew@mail.gmail.com">
      <div dir="ltr">
        <div dir="ltr">
          <div>
            <div>
              <ul>
                <li>Is the customer ready to pay for the additional cost
                  that accrue from IPv6 deployment?</li>
              </ul>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <p>There should not be additional costs to customers for IPv6.
      Instead, look at the cost reduction of IPv6:</p>
    <ol>
      <li>If you will need IPv4 addresses from Afrinic in 2020 or 2021,
        you will not be able to get them. You will have to buy them from
        somebody else in Africa, which (if they cost the same in Africa
        as the rest of the world) by that time will cost US$40-50 each.
        <br>
      </li>
      <li>If you use CGN now (for instance, if you are a mobile
        provider), you can reduce how much money you spend for CGN. If
        you will outgrow your CGN box in a year, or five years, then by
        adopting IPv6, you will have less traffic through your CGN, and
        may not need to replace it. I know some mobile carriers who have
        cut their costs in half by adopting IPv6.</li>
    </ol>
    <p>I think the question to consider is whether customers will pay
      for the additional cost of IPv4?<br>
    </p>
    <blockquote type="cite"
cite="mid:CAGK4d0_kv8gJHgRU_HUyn__HGjELCmLEDqCKqFxXHBDxK209Ew@mail.gmail.com">
      <div dir="ltr">
        <div dir="ltr">
          <div>
            <div>
              <ul>
                <li>Who burns the cost of training and re-training and
                  that of the challenges of the IPv6</li>
              </ul>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <p>Afrinic is on your side here. Their IPv6 Helpdesk is amazing, and
      their training is fantastic. Ask them for help, and what it would
      take to get training near you. Also, when Afrinic IPv6 training
      comes to your country, during a meeting or independently, send
      everyone! After that training, every network engineer, government
      IT manager, and software developer in the country should be
      building IPv6 into everything they do.</p>
    <p>Afrinic may be the best of the RIRs when it comes to IPv6
      deployment support. I've made a point of telling the other RIRs to
      pay attention to what Mukom is doing. <br>
    </p>
    <blockquote type="cite"
cite="mid:CAGK4d0_kv8gJHgRU_HUyn__HGjELCmLEDqCKqFxXHBDxK209Ew@mail.gmail.com">
      <div dir="ltr">
        <div dir="ltr">
          <div>
            <div>
              <ul>
                <li>Are there any form of support or incentives to help
                  help ISPs, big tech company transition to IPv6?</li>
              </ul>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <p>The government incentive I mentioned above should help, as well
      as the cost savings (avoiding new CGN or buying IPv4). <br>
    </p>
    <blockquote type="cite"
cite="mid:CAGK4d0_kv8gJHgRU_HUyn__HGjELCmLEDqCKqFxXHBDxK209Ew@mail.gmail.com">
      <div dir="ltr">
        <div dir="ltr">
          <div>
            <div>Moreso, IPv6 should be taken to the CEO, Directors, CIO
              as they hold the key to the decision making. <br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <p>Don't forget the marketing people. "We can improve the speed of
      our service/web site by doing this" is pretty great; there are
      many articles about how people are more likely to buy from a
      faster e-commerce site.</p>
    <p>Also, if your web site is faster, you will appear higher in
      Google's search rankings. If you run a company that sells
      bicycles, you know that when people Google "bicycles" you want to
      be the first site they see, not the 15th. Page load speed is one
      of the things Google uses to decide how to rank the results. If
      people are 50% more likely to click on the first three results,
      and 15% more likely to buy from a web site that they don't have to
      wait for, speed is very important to the company. <br>
    </p>
    <p>Asking the hosting company to turn on IPv6 for your web site is a
      very easy way to increase sales.</p>
    <p><br>
    </p>
    <p>Lee<br>
    </p>
    <blockquote type="cite"
cite="mid:CAGK4d0_kv8gJHgRU_HUyn__HGjELCmLEDqCKqFxXHBDxK209Ew@mail.gmail.com">
      <div dir="ltr">
        <div dir="ltr">
          <div><br>
          </div>
          <div>Regards.</div>
          <div>Peter</div>
        </div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Thu, Mar 14, 2019 at 11:52
          PM Toyin Oloniteru <<a
            href="mailto:toyin.oloniteru@gmail.com"
            moz-do-not-send="true">toyin.oloniteru@gmail.com</a>>
          wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px
          0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <p dir="ltr">On IPv6 Adoption and Usage</p>
          <p dir="ltr">I think we are missing the Public Policy Agenda
            Setting elements.  We are excessively focused on the
            technology side. We are lacking in the media and
            communication strategy area,  which must be dealt with. For
            example are we educating and informing the public properly
            and sufficiently on:<br>
            a. The reason for IPv6 though IPv4 works<br>
            b.  The relationship between IPv6 and IoTs in particular and
            emerging technologies generally - robotics,  sensors and
            their use cases/applications<br>
            c.  Propositions on transition from IPv4 to IPv6<br>
            d.  Push for c)  above at select public sector organizations
            and Higher Educational Institutions (HEIs). Push for these
            organizations to start making budget proposals to their
            approving authorities on IPv4 to IPv6 transition. Let the
            authorities decline. It is part of public policies agenda
            setting. </p>
          <p dir="ltr">My recommendations <br>
            1. Start building media awareness strategy through working
            groups <br>
            2. Be more aggressive in the area of IPv4 to IPv6 Transition
            Forum <br>
            & Workshops and conference organising<br>
            3. Work on Public Policy Agenda setting Media (Traditional
            and Digital)  strategy <br>
            4. Bring together the supply side (technology/solution
            providers)  and demand side (users - current and
            prospectives)  on the subject matter</p>
          <p dir="ltr">The above are my immediate a little contribution.</p>
          <p dir="ltr">Sincerely. </p>
          <p dir="ltr">HHI Olutoyin J Oloniteru <br>
            Abuja,  Nigeria. </p>
          <div class="gmail_quote">On Mar 14, 2019 8:08 PM, "Akinremi
            Peter Taiwo" <<a href="mailto:compsoftnet@gmail.com"
              target="_blank" moz-do-not-send="true">compsoftnet@gmail.com</a>>
            wrote:<br type="attribution">
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex">
              <div dir="ltr">I quite agree with you Kolawole that more
                awareness of IPv6 is needed. But thinking from a
                business perspective, awareness wouldn't really matter
                if old technology is working and still given a
                satisfactory results. I probably believe that it is TIME
                that would determine the rate of IPv6 adoption. 
                <div><br>
                </div>
                <div>Regards.</div>
                <div>Peter</div>
              </div>
              <br>
              <div class="gmail_quote">
                <div dir="ltr" class="gmail_attr">On Thu, Mar 14, 2019
                  at 1:58 PM kolawole Adewale <<a
                    href="mailto:harnthny@gmail.com" target="_blank"
                    moz-do-not-send="true">harnthny@gmail.com</a>>
                  wrote:<br>
                </div>
                <blockquote class="gmail_quote" style="margin:0px 0px
                  0px 0.8ex;border-left:1px solid
                  rgb(204,204,204);padding-left:1ex">
                  <p dir="ltr">More awareness still needs to be done in
                    the areas of benfits. I feel tech operators in
                    Africa, especially (medium ones)feel reluctant to
                    migrate to IPv6 because of their lack of awareness
                    the IPv6 brings.<br>
                    Kudos to AFRINIC on thier efforts.<br>
                    On 6 Dec 2018 7:48 pm, <<a
                      href="mailto:afripv6-discuss-request@afrinic.net"
                      target="_blank" moz-do-not-send="true">afripv6-discuss-request@afrinic.net</a>>
                    wrote:<br>
                    ><br>
                    > Send AfrIPv6-Discuss mailing list submissions
                    to<br>
                    >         <a
                      href="mailto:afripv6-discuss@afrinic.net"
                      target="_blank" moz-do-not-send="true">afripv6-discuss@afrinic.net</a><br>
                    ><br>
                    > To subscribe or unsubscribe via the World Wide
                    Web, visit<br>
                    >         <a
                      href="https://lists.afrinic.net/mailman/listinfo/afripv6-discuss"
                      target="_blank" moz-do-not-send="true">https://lists.afrinic.net/mailman/listinfo/afripv6-discuss</a><br>
                    > or, via email, send a message with subject or
                    body 'help' to<br>
                    >         <a
                      href="mailto:afripv6-discuss-request@afrinic.net"
                      target="_blank" moz-do-not-send="true">afripv6-discuss-request@afrinic.net</a><br>
                    ><br>
                    > You can reach the person managing the list at<br>
                    >         <a
                      href="mailto:afripv6-discuss-owner@afrinic.net"
                      target="_blank" moz-do-not-send="true">afripv6-discuss-owner@afrinic.net</a><br>
                    ><br>
                    > When replying, please edit your Subject line so
                    it is more specific<br>
                    > than "Re: Contents of AfrIPv6-Discuss
                    digest..."<br>
                    ><br>
                    ><br>
                    > Today's Topics:<br>
                    ><br>
                    >    1. Re: Finding solutions to things that stop
                    people moving to<br>
                    >       IPv6 (Noureddine IDBOUFKER)<br>
                    ><br>
                    ><br>
                    >
                    ----------------------------------------------------------------------<br>
                    ><br>
                    > Message: 1<br>
                    > Date: Thu, 6 Dec 2018 18:47:25 +0000 (UTC)<br>
                    > From: Noureddine IDBOUFKER <<a
                      href="mailto:n_idboufker@yahoo.fr" target="_blank"
                      moz-do-not-send="true">n_idboufker@yahoo.fr</a>><br>
                    > To: <a
                      href="mailto:afripv6-discuss@afrinic.net"
                      target="_blank" moz-do-not-send="true">afripv6-discuss@afrinic.net</a><br>
                    > Subject: Re: [AfrIPv6-Discuss] Finding
                    solutions to things that stop<br>
                    >         people moving to IPv6<br>
                    > Message-ID: <<a
                      href="mailto:152027882.5323643.1544122045102@mail.yahoo.com"
                      target="_blank" moz-do-not-send="true">152027882.5323643.1544122045102@mail.yahoo.com</a>><br>
                    > Content-Type: text/plain; charset="utf-8"<br>
                    ><br>
                    > Sure there are many opportunities behind
                    Transition to IPv6 but unfortunately, for African
                    Operators in each country, there is also a risk.
                    Every day elapsed before this transition moves them
                    towards a very risky situation. I talk about
                    Business and also technical risks. Unfortunately,
                    the majority of operators has an urgency mindset.??I
                    am really convinced that in order to encourage them
                    to transit to IPv6, African Communities has to focus
                    on risks and the urgency aspect of the transition.
                    For example leading studies in order to produce a
                    kind of SWOT Matrix, adapted to the African context,
                    establishing Strengths, Weaknesses, Threats and
                    Opportunities.<br>
                    >
                    Regards-----------------------------------------------<br>
                    > Noureddine IDBOUFKERhttps://<a
                      href="http://www.linkedin.com/in/idboufkernoureddine/"
                      target="_blank" moz-do-not-send="true">www.linkedin.com/in/idboufkernoureddine/</a><br>
                    ><br>
                    ><br>
                    >     Le jeudi 6 d?cembre 2018 ? 15:51:06 UTC+1,
                    Lee Howard <<a
                      href="mailto:lee.howard@retevia.net"
                      target="_blank" moz-do-not-send="true">lee.howard@retevia.net</a>>
                    a ?crit :  <br>
                    ><br>
                    ><br>
                    ><br>
                    ><br>
                    >  On 12/6/18 5:22 AM, Noureddine IDBOUFKER via
                    AfrIPv6-Discuss wrote:<br>
                    ><br>
                    ><br>
                    >   I think that Top management is not enough
                    aware of business opportunities behind IPv6
                    migration.? Sure IPv6 will give them the opportunity
                    to address a high number of objects, equipements,
                    services,....? but it is not limited to that. Top
                    management has to encourage their people to be
                    express their innovation capabilities in a such a
                    way to contribute  to the developpement of Value
                    Added Services.? Providers who will not propose new
                    competitive service catalogue will simply die in
                    globalized world. Top management has to know hat
                    IPv6 is a real pillar of IT governance. <br>
                    ><br>
                    > I agree with that. I have several presentations
                    on business reasons for IPv6, which I imagine
                    overlap with AFRINIC's IPv6 for Executives training:<br>
                    ><br>
                    >    - Not running out of addresses, so you can
                    keep adding customers<br>
                    >    - Faster [1]   <br>
                    ><br>
                    >    - Because it's faster, Google page rank is
                    higher; more customers see your web site   <br>
                    ><br>
                    >    - Because it's faster, users spend more time
                    on the page; more ad revenue   <br>
                    ><br>
                    >    - IPv6 is on by default; may present
                    security risks if not secured<br>
                    >    - Use addresses to identify services; easier
                    policy routing, ACLs, security, troubleshooting,
                    etc.<br>
                    >    - New diagnostic tools PDM [rfc8250] and
                    maybe M-PDM [draft-fear-ippm-mpdm]<br>
                    >    - Simpler container networking [2]   <br>
                    ><br>
                    >    - Segment Routing with IPv6: no
                    MPLS/LDP/RSVP-TE/NSH, it's all just IP. [3]   <br>
                    ><br>
                    ><br>
                    > The last few are cutting-edge developments that
                    are not widely available yet, but are examples of
                    innovations enabled by IPv6. I didn't even list
                    "It's not NAT" because you're likely to use some
                    kind of address sharing to reach legacy IPv4 sites,
                    but that need declines as others deploy, and it may
                    be cheaper than NAT44.<br>
                    ><br>
                    > IPv6 is cool.<br>
                    ><br>
                    ><br>
                    > Lee<br>
                    ><br>
                    ><br>
                    > [1] <a
                      href="https://stats.labs.apnic.net/v6perf/XB"
                      target="_blank" moz-do-not-send="true">https://stats.labs.apnic.net/v6perf/XB</a>
                    <br>
                    ><br>
                    ><br>
                    > [2] <a
                      href="https://www.youtube.com/watch?v=eF50OxZ5u4o"
                      target="_blank" moz-do-not-send="true">https://www.youtube.com/watch?v=eF50OxZ5u4o</a>
                    <br>
                    ><br>
                    > [3] <a
                      href="https://www.youtube.com/watch?v=ZUN68P6UAn0"
                      target="_blank" moz-do-not-send="true">https://www.youtube.com/watch?v=ZUN68P6UAn0</a><br>
                    ><br>
                    ><br>
                    ><br>
                    >    Regards?<br>
                    >  
                    -----------------------------------------------<br>
                    >  Noureddine IDBOUFKER  <br>
                    ><br>
                    >       Le jeudi 6 d?cembre 2018 ? 10:57:24
                    UTC+1, JORDI PALET MARTINEZ via AfrIPv6-Discuss <<a
                      href="mailto:afripv6-discuss@afrinic.net"
                      target="_blank" moz-do-not-send="true">afripv6-discuss@afrinic.net</a>>
                    a ?crit :  <br>
                    ><br>
                    ><br>
                    > Operators are informed, if you speak about
                    ?engineers?, the problem is to inform the CEOs of
                    operator AND the CEOs of important companies in each
                    country (financial sectors, companies that export or
                    have relevant web sites, etc.).<br>
                    ><br>
                    >  ?<br>
                    ><br>
                    > I recall ARIN did sent a letter to them (in
                    their region) a few years ago.<br>
                    ><br>
                    ><br>
                    >  Regards,<br>
                    ><br>
                    > Jordi<br>
                    ><br>
                    >  ?<br>
                    ><br>
                    >  ?<br>
                    ><br>
                    >  ?<br>
                    ><br>
                    > De: Pascal ANDRIANISA <<a
                      href="mailto:pascal@irenala.edu.mg"
                      target="_blank" moz-do-not-send="true">pascal@irenala.edu.mg</a>><br>
                    >  Responder a: IPv6 in Africa Discussions <<a
                      href="mailto:afripv6-discuss@afrinic.net"
                      target="_blank" moz-do-not-send="true">afripv6-discuss@afrinic.net</a>><br>
                    >  Fecha: jueves, 6 de diciembre de 2018, 10:47<br>
                    >  Para: IPv6 in Africa Discussions <<a
                      href="mailto:afripv6-discuss@afrinic.net"
                      target="_blank" moz-do-not-send="true">afripv6-discuss@afrinic.net</a>><br>
                    >  Asunto: Re: [AfrIPv6-Discuss] Finding
                    solutions to things that stop people moving to IPv6<br>
                    ><br>
                    >  ?<br>
                    >     Dear All,<br>
                    ><br>
                    > I think there is also another solution which is
                    to inform the operators in each country of the
                    situation because if only the members who will apply
                    IPv6 it will not be possible to use it optimally.<br>
                    > I do not know if a provision to that effect has
                    already been taken but I think that all the members
                    are aware of the situation.<br>
                    ><br>
                    > Best regard,   Pascal Heriliva ANDRIANISA<br>
                    >  Webmaster i RENALA<br>
                    >  Research and Education Network for Academic
                    and Learning Activities - <a
                      href="http://www.irenala.edu.mg/" target="_blank"
                      moz-do-not-send="true">http://www.irenala.edu.mg/</a><br>
                    >  Porte 201 - Minist?re de l'Enseignement
                    Sup?rieur et de la Recherche Scientifique -
                    Fiadanana<br>
                    >  GSM :+261 (0) 32 46 680 29 |? +261 (0) 34 30
                    680 29   ?    De: "Mukom Akong T." <<a
                      href="mailto:mukom.tamon@gmail.com"
                      target="_blank" moz-do-not-send="true">mukom.tamon@gmail.com</a>><br>
                    > ?: "IPv6 in Africa" <<a
                      href="mailto:afripv6-discuss@afrinic.net"
                      target="_blank" moz-do-not-send="true">afripv6-discuss@afrinic.net</a>><br>
                    > Envoy?: Jeudi 6 D?cembre 2018 06:41:29<br>
                    > Objet: Re: [AfrIPv6-Discuss] Finding solutions
                    to things that stop people moving to IPv6   ?       
                      <br>
                    ><br>
                    > ><br>
                    > > Consumers are unaware of IPv6, so it's not
                    part of their buying decision. If something doesn't
                    make consumer buy boxes, vendors don't do it. I do
                    not think consumer education about IP is a good
                    idea.<br>
                    ><br>
                    ><br>
                    ><br>
                    > Neither do I. Consumers don't DIRECTLY care
                    about IP (whether v4 or v6). But they do care about
                    other features that may be only possible (or easier,
                    or cheaper) with v6.<br>
                    ><br>
                    ><br>
                    > This is one place where I see the role of
                    governments. In the interest of national
                    development, just ban importation and sale of legacy
                    equipment. Similar to what is already done with type
                    approval in telecommunications today.<br>
                    ><br>
                    ><br>
                    ><br>
                    > > ISPs buying cheap boxes and not paying
                    anything for support, so they can't get upgrades.<br>
                    > > Foreign ISPs dumping volumes of used CPE,
                    which get resold at deep discounts.<br>
                    ><br>
                    ><br>
                    > I've been screaming about this for years. Even
                    worse, some of it is going to be "sold" as "next
                    generation Internet aid or technical corporation")
                    which further cripples IPv6 deployment.<br>
                    ><br>
                    > ><br>
                    > > Something that has worked for some
                    companies is an "ISP Certified" sticker. CPE vendors
                    could apply to an ISP, and pay the costs of testing.
                    If the tests complied with the ISP's requirements,
                    which might include MAP, lw4o6, or 464xlat support,
                    the vendor is allowed to put a sticker on their box
                    saying, "This device certified for use with $ISP."
                    There might be a business opportunity for someone
                    who can set up a really good CPE testing lab, so
                    ISPs could outsource their testing and
                    certification.<br>
                    ><br>
                    ><br>
                    > In addition, I believe that with two days of
                    training (regulators and customs) and the
                    appropriate infrastructure and a PROCESS, we can
                    help a government implement type approval for IPv6.
                    Any regulator that wishes to do this should reach
                    out and join the waiting list by taking the
                    Government IPv6 Readiness Self Assessment at ?<br>
                    ><br>
                    > ENGLISH ? <a
                      href="https://vox.afrinic.net/465923?lang=en"
                      target="_blank" moz-do-not-send="true">https://vox.afrinic.net/465923?lang=en</a><br>
                    > FRENCH ? ?<a
                      href="https://vox.afrinic.net/465923?lang=fr"
                      target="_blank" moz-do-not-send="true">https://vox.afrinic.net/465923?lang=fr</a><br>
                    ><br>
                    ><br>
                    > > 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<br>
                    ><br>
                    ><br>
                    > I agree with the above. The solution is not
                    just another open "discussion" where people who have
                    not even started any kind of deployment, or even
                    have a fair idea of what percentage of equipment
                    might or might not be v6 ready go on an on about
                    problems they've only heard about.<br>
                    ><br>
                    ><br>
                    > ><br>
                    > > Should we have a round table discussion at
                    AIS? How can we identify and make progress on
                    resolving issues with IPv6?<br>
                    > ><br>
                    ><br>
                    ><br>
                    > Perhaps we can start with a mailing list thread
                    of SPECIFIC issues people have encountered while
                    attempting a deployment on this mailing list, then
                    build up to a webinar or discussion at AIS.<br>
                    ><br>
                    ><br>
                    > There are probably about 400million users using
                    IPv6 today and growing, someone somewhere has solved
                    those problems.<br>
                    ><br>
                    ><br>
                    > > The common theme in my answers above is
                    that more people running IPv6 provides more weight
                    in solving problems. If everyone would take a couple
                    of hours to do three things, we'd have a very broad
                    base of common experience to draw from:<br>
                    > ><br>
                    > > 1. Write an address plan. Don't worry if
                    it takes several revisions, that's normal.<br>
                    > ><br>
                    > > 2. Apply to Afrinic for IPv6 addresses.<br>
                    > ><br>
                    > > 3. Announce the IPv6 addresses and route
                    them on your backbone.<br>
                    ><br>
                    ><br>
                    > These are things that we've helped operators
                    implement in 1 day at our deployathons (or 6 two
                    hour sessions during helpdesk calls). It's
                    surprising how many operators need help with their
                    address planning. Which is why not only do we teach
                    them how to determine how much space they get, but
                    also how to implement them in an IPAM.? For those
                    interested, a video of a highly attended and rated
                    AFRINIC webinar can be found at<br>
                    ><br>
                    ><br>
                    > <a
                      href="https://www.youtube.com/watch?v=CFIVQ_Z9je8&t=542s"
                      target="_blank" moz-do-not-send="true">https://www.youtube.com/watch?v=CFIVQ_Z9je8&t=542s</a><br>
                    ><br>
                    > Step by step walk-through of address planning
                    best practices and implementation in an IPAM ---- no
                    maths!<br>
                    ><br>
                    ><br>
                    > ><br>
                    > > AFRINIC's training and IPv6 Helpdesk are
                    great resources. <br>
                    ><br>
                    ><br>
                    > The premise behind the helpdesk is this: We can
                    find ONE operator a month that's committed to
                    deploying IPv6, we keep providing targeted training
                    and coaching to move them from one deployment
                    milestone to another until we get stuck with
                    incompatible equipment or internal collaboration
                    issues. All it takes is about 4 hours investment per
                    week. If you are interested, make a request at??<br>
                    ><br>
                    ><br>
                    > <a href="http://bit.ly/6deployEN"
                      target="_blank" moz-do-not-send="true">bit.ly/6deployEN</a>?
                    ?(english)<br>
                    > <a href="http://bit.ly/6deployFR"
                      target="_blank" moz-do-not-send="true">bit.ly/6deployFR</a>?
                    ? (french)<br>
                    ><br>
                    > As we do this, we're also building an
                    tremendous amount of intel on what actually HOLDS
                    IPv6 deployment back from real operators attempting
                    to deploy it and so far with over 45 tickets, the
                    evidence indicates that incompatible equipment is
                    not in the top 5.?  We're also realising that that
                    argument from big operators about "customers aren't
                    asking for it" is not true. We know of large
                    operators that within 2 months have received
                    explicitly written requests to enable IPv6 from
                    large corporate customers. You don't want to see
                    their response :(   ?  If you want to host one of
                    our DEPLOYATHON sessions in your country?   ?  - 5%
                    teaching, 95% DOing   -?using our Prototype??
                    Validate ? Develop?? Deploy framework   - enables
                    you hit a measurable deployment milestone within 8
                    hours   ?  you can apply at:??<a
href="https://vox.afrinic.net/189828?lang=en?(or?https://vox.afrinic.net/189828?lang=fr"
                      target="_blank" moz-do-not-send="true">https://vox.afrinic.net/189828?lang=en?(or?https://vox.afrinic.net/189828?lang=fr</a>
                    in french)   ?  And for those who are still
                    wondering how ready or not their organisations are,
                    take our free Organisational IPv6 Readiness
                    Assessment at??<a
                      href="https://vox.afrinic.net/651525?lang=en"
                      target="_blank" moz-do-not-send="true">https://vox.afrinic.net/651525?lang=en</a>?
                    (or?<a href="https://vox.afrinic.net/651525?lang=fr"
                      target="_blank" moz-do-not-send="true">https://vox.afrinic.net/651525?lang=fr</a>
                    in French)   <br>
                    > The results might provide pointers where to
                    start the process.   ?  Until next time ..... be
                    EXCELLENT<br>
                    ><br>
                    > -- <br>
                    ><br>
                    > Mukom Akong T.<br>
                    ><br>
                    > LinkedIn:Mukom ?| ?twitter: @perfexcellent ?<br>
                    ><br>
                    >
------------------------------------------------------------------------------------------------------------------------------------------<br>
                    > ?When you work, you are the FLUTE through whose
                    lungs the whispering of the hours turns to MUSIC" -
                    Kahlil Gibran<br>
                    >
------------------------------------------------------------------------------------------------------------------------------------------- 
                             ? <br>
                    > _______________________________________________<br>
                    > AfrIPv6-Discuss mailing list<br>
                    > <a href="mailto:AfrIPv6-Discuss@afrinic.net"
                      target="_blank" moz-do-not-send="true">AfrIPv6-Discuss@afrinic.net</a><br>
                    > <a
                      href="https://lists.afrinic.net/mailman/listinfo/afripv6-discuss"
                      target="_blank" moz-do-not-send="true">https://lists.afrinic.net/mailman/listinfo/afripv6-discuss</a> 
                     <br>
                    >  ?<br>
                    ><br>
                    > _______________________________________________
                    AfrIPv6-Discuss mailing list <a
                      href="mailto:AfrIPv6-Discuss@afrinic.net"
                      target="_blank" moz-do-not-send="true">AfrIPv6-Discuss@afrinic.net</a>
                    <a
                      href="https://lists.afrinic.net/mailman/listinfo/afripv6-discuss"
                      target="_blank" moz-do-not-send="true">https://lists.afrinic.net/mailman/listinfo/afripv6-discuss</a>
                    <br>
                    ><br>
                    >  **********************************************<br>
                    >  IPv4 is over<br>
                    >  Are you ready for the new Internet ?<br>
                    >  <a href="http://www.theipv6company.com"
                      target="_blank" moz-do-not-send="true">http://www.theipv6company.com</a><br>
                    >  The IPv6 Company<br>
                    ><br>
                    >  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.<br>
                    ><br>
                    >  
                     _______________________________________________<br>
                    >  AfrIPv6-Discuss mailing list<br>
                    >  <a href="mailto:AfrIPv6-Discuss@afrinic.net"
                      target="_blank" moz-do-not-send="true">AfrIPv6-Discuss@afrinic.net</a><br>
                    >  <a
                      href="https://lists.afrinic.net/mailman/listinfo/afripv6-discuss"
                      target="_blank" moz-do-not-send="true">https://lists.afrinic.net/mailman/listinfo/afripv6-discuss</a><br>
                    ><br>
                    >  
                    _______________________________________________<br>
                    > AfrIPv6-Discuss mailing list<br>
                    > <a href="mailto:AfrIPv6-Discuss@afrinic.net"
                      target="_blank" moz-do-not-send="true">AfrIPv6-Discuss@afrinic.net</a><br>
                    > <a
                      href="https://lists.afrinic.net/mailman/listinfo/afripv6-discuss"
                      target="_blank" moz-do-not-send="true">https://lists.afrinic.net/mailman/listinfo/afripv6-discuss</a><br>
                    ><br>
                    >
                     _______________________________________________<br>
                    > AfrIPv6-Discuss mailing list<br>
                    > <a href="mailto:AfrIPv6-Discuss@afrinic.net"
                      target="_blank" moz-do-not-send="true">AfrIPv6-Discuss@afrinic.net</a><br>
                    > <a
                      href="https://lists.afrinic.net/mailman/listinfo/afripv6-discuss"
                      target="_blank" moz-do-not-send="true">https://lists.afrinic.net/mailman/listinfo/afripv6-discuss</a><br>
                    ><br>
                    > -------------- next part --------------<br>
                    > An HTML attachment was scrubbed...<br>
                    > URL: <<a
href="https://lists.afrinic.net/pipermail/afripv6-discuss/attachments/20181206/667398e3/attachment.html"
                      target="_blank" moz-do-not-send="true">https://lists.afrinic.net/pipermail/afripv6-discuss/attachments/20181206/667398e3/attachment.html</a>><br>
                    ><br>
                    > ------------------------------<br>
                    ><br>
                    > Subject: Digest Footer<br>
                    ><br>
                    > _______________________________________________<br>
                    > AfrIPv6-Discuss mailing list<br>
                    > <a href="mailto:AfrIPv6-Discuss@afrinic.net"
                      target="_blank" moz-do-not-send="true">AfrIPv6-Discuss@afrinic.net</a><br>
                    > <a
                      href="https://lists.afrinic.net/mailman/listinfo/afripv6-discuss"
                      target="_blank" moz-do-not-send="true">https://lists.afrinic.net/mailman/listinfo/afripv6-discuss</a><br>
                    ><br>
                    ><br>
                    > ------------------------------<br>
                    ><br>
                    > End of AfrIPv6-Discuss Digest, Vol 146, Issue
                    12<br>
                    >
                    ************************************************<br>
                  </p>
                  _______________________________________________<br>
                  AfrIPv6-Discuss mailing list<br>
                  <a href="mailto:AfrIPv6-Discuss@afrinic.net"
                    target="_blank" moz-do-not-send="true">AfrIPv6-Discuss@afrinic.net</a><br>
                  <a
                    href="https://lists.afrinic.net/mailman/listinfo/afripv6-discuss"
                    rel="noreferrer" target="_blank"
                    moz-do-not-send="true">https://lists.afrinic.net/mailman/listinfo/afripv6-discuss</a><br>
                </blockquote>
              </div>
              <br clear="all">
              <div><br>
              </div>
              -- <br>
              <div dir="ltr">
                <table cellspacing="0" cellpadding="0" border="0">
                  <tbody>
                    <tr>
                      <td
style="line-height:0;vertical-align:bottom;padding-right:10px;padding-top:20px;padding-bottom:20px"
                        width="107" valign="bottom" align="left"> <a
href="https://about.me/petertaiwoakinremi?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=gmail_api&utm_content=thumb"
                          style="text-decoration:none" target="_blank"
                          moz-do-not-send="true"> <img
src="https://thumbs.about.me/thumbnail/users/p/e/t/petertaiwoakinremi_emailsig.jpg?_1540687942_056"
                            alt="" style="margin: 0px; padding: 0px;
                            display: block; border: 1px solid rgb(238,
                            238, 238);" moz-do-not-send="true"
                            width="105" height="70"> </a> </td>
                      <td
style="line-height:1.1;vertical-align:bottom;padding-top:20px;padding-bottom:20px"
                        valign="bottom" align="left"> <img
                          src="https://about.me/t/sig?u=petertaiwoakinremi"
                          style="border: 0px; margin: 0px; padding: 0px;
                          overflow: hidden;" moz-do-not-send="true"
                          width="1" height="1">
                        <div
style="font-size:18px;font-weight:bold;color:rgb(51,51,51);font-family:"Proxima
                          Nova",Helvetica,Arial,sans-serif">Peter
                          Taiwo Akinremi</div>
                        <a
href="https://about.me/petertaiwoakinremi?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=gmail_api&utm_content=thumb"
style="text-decoration:none;font-size:12px;color:rgb(43,130,173);font-family:"Proxima
                          Nova",Helvetica,Arial,sans-serif"
                          target="_blank" moz-do-not-send="true">about.me/petertaiwoakinremi
                        </a> </td>
                    </tr>
                  </tbody>
                </table>
              </div>
              <br>
              _______________________________________________<br>
              AfrIPv6-Discuss mailing list<br>
              <a href="mailto:AfrIPv6-Discuss@afrinic.net"
                target="_blank" moz-do-not-send="true">AfrIPv6-Discuss@afrinic.net</a><br>
              <a
                href="https://lists.afrinic.net/mailman/listinfo/afripv6-discuss"
                rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.afrinic.net/mailman/listinfo/afripv6-discuss</a><br>
              <br>
            </blockquote>
          </div>
          _______________________________________________<br>
          AfrIPv6-Discuss mailing list<br>
          <a href="mailto:AfrIPv6-Discuss@afrinic.net" target="_blank"
            moz-do-not-send="true">AfrIPv6-Discuss@afrinic.net</a><br>
          <a
            href="https://lists.afrinic.net/mailman/listinfo/afripv6-discuss"
            rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.afrinic.net/mailman/listinfo/afripv6-discuss</a><br>
        </blockquote>
      </div>
      <br clear="all">
      <div><br>
      </div>
      -- <br>
      <div dir="ltr" class="gmail_signature">
        <table cellspacing="0" cellpadding="0" border="0">
          <tbody>
            <tr>
              <td
style="line-height:0;vertical-align:bottom;padding-right:10px;padding-top:20px;padding-bottom:20px"
                width="107" valign="bottom" align="left"> <a
href="https://about.me/petertaiwoakinremi?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=gmail_api&utm_content=thumb"
                  style="text-decoration:none" target="_blank"
                  moz-do-not-send="true"> <img
src="https://thumbs.about.me/thumbnail/users/p/e/t/petertaiwoakinremi_emailsig.jpg?_1540687942_056"
                    alt="" style="margin: 0px; padding: 0px; display:
                    block; border: 1px solid rgb(238, 238, 238);"
                    moz-do-not-send="true" width="105" height="70"> </a>
              </td>
              <td
style="line-height:1.1;vertical-align:bottom;padding-top:20px;padding-bottom:20px"
                valign="bottom" align="left"> <img
                  src="https://about.me/t/sig?u=petertaiwoakinremi"
                  style="border: 0px; margin: 0px; padding: 0px;
                  overflow: hidden;" moz-do-not-send="true" width="1"
                  height="1">
                <div
style="font-size:18px;font-weight:bold;color:rgb(51,51,51);font-family:"Proxima
                  Nova",Helvetica,Arial,sans-serif">Peter Taiwo
                  Akinremi</div>
                <a
href="https://about.me/petertaiwoakinremi?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=gmail_api&utm_content=thumb"
style="text-decoration:none;font-size:12px;color:rgb(43,130,173);font-family:"Proxima
                  Nova",Helvetica,Arial,sans-serif" target="_blank"
                  moz-do-not-send="true">about.me/petertaiwoakinremi </a>
              </td>
            </tr>
          </tbody>
        </table>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
AfrIPv6-Discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:AfrIPv6-Discuss@afrinic.net">AfrIPv6-Discuss@afrinic.net</a>
<a class="moz-txt-link-freetext" href="https://lists.afrinic.net/mailman/listinfo/afripv6-discuss">https://lists.afrinic.net/mailman/listinfo/afripv6-discuss</a>
</pre>
    </blockquote>
  </body>
</html>