<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br><br>Sent from my iPad</div><div><br>On Jan 15, 2013, at 9:55 AM, Maina Noah <<a href="mailto:mainanoa@gmail.com">mainanoa@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">Well Owen i here you and i understand you have more experience deploying v6 but thats not to say to gonna take that long. Its not rocket science that is what i am saying and there so many work-around to everything. In regards to provisioning systems, a typical organization would have not so many hence quite simple and for end users SLAAC and DHCP is workround and this works like magic...for address management, come on, same ways we manage v4, only thing which changes is the addresses....internal softwares, u mean Windows xp '-) lol <div>
<br></div></div></div></blockquote><div><br></div>One provisioning system that stores it's IP information as 32-bit integers may take 6-months or more to update the software in order to incorporate IPv6 address management (at the network prefix level, not the host level).<div><br></div><div><blockquote type="cite"><div><div dir="ltr"><div style="">In terms of large-scale deployment, well i could agree with you on that but in the African context we are talking of multi-national telco's and ISP's the rest of the networks are very small... so 6months is way to long.</div></div></div></blockquote><div><br></div>Yes, the multinational telcos are the ones that concern me the most in this context because if they don't make IPv6 available to the smaller networks, things get pretty dicey all the way around.</div><div><br></div><div>Owen</div><div><br><blockquote type="cite"><div><div dir="ltr">
<div style=""><br></div><div style="">Maina Noah</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 15 January 2013 22:42, Owen DeLong <span dir="ltr"><<a href="mailto:owen@delong.com" target="_blank">owen@delong.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><div>On Jan 15, 2013, at 11:34 AM, Maina Noah <<a href="mailto:mainanoa@gmail.com" target="_blank">mainanoa@gmail.com</a>> wrote:</div>
<br><blockquote type="cite"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On 15 January 2013 21:58, Owen DeLong <span dir="ltr"><<a href="mailto:owen@delong.com" target="_blank">owen@delong.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><div>On Jan 15, 2013, at 10:21 AM, Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com" target="_blank">seun.ojedeji@gmail.com</a>> wrote:</div>
<br><blockquote type="cite"><p>On Jan 15, 2013 2:58 PM, "Andrew Alston" <<a href="mailto:alston.networks@gmail.com" target="_blank">alston.networks@gmail.com</a>> wrote:<br>
><br>
> Hi Maina,<br>
><br>
> <br>
><br>
> I personally believe that the problem is two-fold. Firstly, the community tends to resist change and the argument always surfaces, why implement something that isn’t going to generate revenue. The fact is though that many of us have been saying for years and years that IPv6 is not about revenue generation, it’s about revenue retention. When the day arrives that customers cannot access something elsewhere in the rest of the world because its gone IPv6 only<br>
><br>
I don't get it Andrew you are making it look like it's either now or never ;-) will v6 allocation end at this future your are painting here?<br>
and an ISP cannot offer IPv6, at that point, the customer is going to walk and go somewhere that can give him full access to the Net, and the revenue from that customer is gone. <br>
><br></p></blockquote><div><br></div>It's not now or never, but if you wait for the customer to demand it, it's too late. Deploying IPv6 is not an instantaneous process. You can't get the request from the customer today and have IPv6 delivered to them in a stable, scalable manner in 30 days. You're looking at a process which could take as little as 6 months on a small dynamic network or as much as 3-5 years in a large-scale organization.</div>
<div><br></div></div></blockquote><div> </div><div>Owen from my experience deploying IPv6 for one of the ISP in East Africa, i think that is a bit over-exaggerated when you say 6 months. A typical ISP with for instance 10 POP's at minimum could deploy v6 across the core in a month or so ...6 months is way to long even if they didn't plan well it could take at-most 3 moons…We have mailing list like afnog etc where folks can exchange ideas hence make life easier in case one was stuck.</div>
</div></div></div></blockquote><div><br></div>Across the core, sure. But what about provisioning systems, address management, monitoring, any internal software, etc.?</div><div><br></div><div>There's a lot more to deploying IPv6 to customers in a sustainable scalable manner than merely getting addresses on a few core routers.</div>
<div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">
<div>So guys don't be scared 3-5 Years is way to long unless if that large-scale organization in question has very lazy net-engineers !!!!!</div><div><br></div></div></div></div></blockquote><div><br></div></div>How many large-scale organizations have you worked with on IPv6 deployment? I'm talking full deployment, not just the core routers… All the way to the edge and in a sustainable and scalable way. A way that IPv6 is a routine product, not an exception or one-off for a few customers.<div>
<br></div><div>Also, let's define the term large-scale… We're talking 20,000 employees (enterprise) or more than 1,000,000 customers (ISP).</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Owen</div>
<div><br></div></font></span></div></blockquote></div><br></div>
</div></blockquote></div></body></html>