[afripv6-discuss] Fwd: [afgwg-discuss] 6 Steps for Jump-Starting IPv6 Adoption in Government

Mark Elkins mje at posix.co.za
Thu May 24 19:34:45 SAST 2012


On Thu, 2012-05-24 at 07:57 +0100, Victor Ndonnang wrote:
> Dear Nabil,
> 
>  
> 
> Thank you very much for sharing your experience. Can you tell us more
> about how you managed to make your web site IPv6 ready?

I gave a presentation at AfriNIC-6 (five years ago!) which covered what
you ask.
http://www2.afrinic.net/meeting/afrinic-6/agenda.htm#04
http://www2.afrinic.net/meeting/afrinic-6/presentations/1/AFRINIC_6_IPV6_Deployment_Mark.pdf

You can test your IPv6 connectivity by going to secdns2.posix.co.za (a
secondary site I have in London). You'll see your IP address and either
a boring, static Tux [IPv4] or a Joyful, Dancing Tux [IPv6] - concept
inspired by the kame project.


> Best regards,
> 
> Victor.
> 
>  
> 
>  
> 
> De : afripv6-discuss-bounces at afrinic.net
> [mailto:afripv6-discuss-bounces at afrinic.net] De la part de nabil
> benamar
> Envoyé : mercredi 23 mai 2012 23:30
> À : IPv6 in Africa
> Objet : Re: [afripv6-discuss] Fwd: [afgwg-discuss] 6 Steps for
> Jump-Starting IPv6 Adoption in Government
> 
> 
>  
> 
> Dear all,
> 
> I read your discussion about IPv6 deployment in Africa, and I agree
> that when there is a lack of clear plan for migration in ISP side, one
> can do something else to discover the second Internet (with IPv6).
> It's my case! And my website nabilbenamar.com is perhaps, until these
> days, the only one in Morocco which is IPv6 ready!
> 
> regards
> 
> 2012/5/23 Adiel Akplogan <adiel at afrinic.net>
> 
> 
> Begin forwarded message:
> 
> > From: "Adiel A. Akplogan" <adiel at akplogan.com>
> > Date: May 23, 2012 13:50:59 PM GMT+04:00
> > To: afgwg-discuss at afrinic.net
> > Subject: [afgwg-discuss] 6 Steps for Jump-Starting IPv6 Adoption in
> Government
> >
> > You may find this article interesting.
> >
> >
> http://www.govtech.com/policy-management/6-Steps-for-Jump-Starting-IPv6-Adoption-in-Government.html
> >
> > May 22, 2012 By Brian Heaton
> >
> > Confused on how to adopt IPv6 for your state or local government
> website? If so, you’re likely not alone.
> >
> > Sixty percent of enterprise IT teams don’t have an IPv6 plan in
> place, according to a recent survey by Infoblox, a provider of
> automated network controls. But fear not — joining the IPv6 movement
> may be easier than you think.
> >
> > Paul Ebersman, IPv6 evangelist with the Infoblox IPv6 Center of
> Excellence, said that while the change involves Internet connectivity,
> government tech professionals shouldn’t assume the only equipment that
> needs to be IPv6-capable is networking technology. IPv6 is the
> Internet’s next-generation protocol that, unlike the current IPv4
> standard, has essentially an inexhaustible number of IP addresses.
> >
> > “The reality is it’s a complete change in how the Internet works
> below that affects everything,” Ebersman said of IPv6 adoption.
> “Things you don’t think about [such as] hardware, software,
> applications, wireless video cameras, legacy gear in your accounting
> department. You need to discover what all of those things are and see
> if you have a migration path for those devices.”
> >
> > In addition, one of the key steps government agencies should
> consider is making a commitment to only buy new equipment that is IPv6
> compliant. This way, over time a government’s normal technology
> refresh cycle will naturally filter out non-IPv6 devices.
> >
> > Ebersman felt putting that mandate in place would be “huge” for
> governments wanting to move to IPv6, without altering budget practices
> or bid cycles much, except to add an additional requirement to the
> process.
> >
> > Focused specifically on website compatibility, however, the Infoblox
> IPv6 Center of Excellence provided six basic steps that state and
> local governments can take to make their websites accessible to IPv6
> devices:
> >
> >       • Get IPv6 addresses from your Regional Internet Registry
> (RIR) or Internet service provider;
> >       • Get IPv6 connectivity from your ISP;
> >       • Identify candidate Web and DNS server(s) and the supporting
> network(s) for IPv6 adoption;Audit Web and DNS server(s) and the
> supporting network(s) for IPv6 support;
> >       • For Web and DNS server(s) as well as supporting network(s)
> configure dual-stack IPv4/IPv6 (or employ appropriate transition
> technology); and
> >       • Publish IPv6 DNS records (AAAAs) for the main website.
> > IPv6 Needed
> > IP addresses are the identifying numbers given to each device that
> goes online. IPv4, a protocol with those numbers, was launched in 1981
> and has about 4 billion addresses. But with the sharp increase of
> devices connecting to the Internet, the last of those IPv4 number has
> been assigned. To meet the increased demand, IPv6 was created.
> >
> > The challenge facing technology professionals is that IPv4 and IPv6
> can’t be merged. Both versions need to run parallel. There are
> short-term solutions, such as assigning an IPv6 address to a temporary
> IPv4 number, but as more devices connect to the Web inevitably the
> final IPv4 numbers will be used up and those devices will be wholly
> dependent on IPv6 numbers.
> >
> > At some point, domains that aren’t running the IPv6 protocol will
> not be able accessible to those devices operating with only an IPv6 IP
> address, thus the push for IPv6 adoption.
> >
> > So why do some agencies and companies in the U.S. still lack an IPv6
> plan? Ebersman said the delay is likely due to a lack of understanding
> that there actually is an IP address shortage. He explained that the
> U.S. has had a wealth of IPv4 space compared to the rest of the world,
> so the urgency hasn’t been present until now.
> >
> > In addition, mobile connectivity and “bring-your-own-technology”
> initiatives are acting as another driver for IPv6 adoption. In the
> past, handheld devices traditionally didn’t have the bandwidth
> capabilities that computers did, but widespread use of tablets has
> changed the playing field, Ebersman explained.
> >
> > “Even though you don’t think you have a need to provide IPv6
> connectivity, suddenly a whole class of your customers and users that
> you are supporting actually do need to have that,” Ebersman said,
> referring to local and state governments that are now seeing more
> citizens accessing official websites via mobile devices.
> >
> > “While most of the wireless providers are doing transition
> technologies, the performance is not the same as it would be with
> native IPv6,” he added. “There will be a performance difference users
> will see if you enable v6 as well as v4 on your website.”
> >
> > _______________________________________________
> > afgwg-discuss mailing list
> > afgwg-discuss at afrinic.net
> > https://lists.afrinic.net/mailman/listinfo.cgi/afgwg-discuss
> >
> 
> _______________________________________________
> afripv6-discuss mailing list
> afripv6-discuss at afrinic.net
> https://lists.afrinic.net/mailman/listinfo.cgi/afripv6-discuss
> 
> 
> 
> 
> 
> -- 
> 
>  
> 
> 
 <تحياتي ، Cordialement, Regards
> 
> 
>  
> 
> 
>  
> 
> 
 <نبيل بنعمرو Nabil Benamar
> Professor of computer sciences
> Simulation and Modelisation Laboratory
> 
> Human Sciences Faculty of Meknes
> Moulay Ismail University
> Meknes, Morocco
> GSM:  + 212 6 70832236 
> http://nabilbenamar.com/
> 
> 
>  
> 
> 
> --------------------------------------------------------------------------------
> 
> 
>  
> 
> 
> _______________________________________________
> afripv6-discuss mailing list
> afripv6-discuss at afrinic.net
> https://lists.afrinic.net/mailman/listinfo.cgi/afripv6-discuss

-- 
  .  .     ___. .__      Posix Systems - (South) Africa
 /| /|       / /__       mje at posix.co.za  -  Mark J Elkins, Cisco CCIE
/ |/ |ARK \_/ /__ LKINS  Tel: +27 12 807 0590  Cell: +27 82 601 0496

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 4007 bytes
Desc: not available
Url : https://lists.afrinic.net/pipermail/afripv6-discuss/attachments/20120524/364c203d/smime-0001.bin


More information about the afripv6-discuss mailing list