<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Gert Doering ha scritto: <blockquote cite="mid:20100313230015.GE69383@Space.Net" type="cite"> <pre wrap="">Hi, On Sat, Mar 13, 2010 at 12:30:11PM -0800, Edu Abume wrote: </pre> <blockquote type="cite"> <pre wrap="">Does anyone know the average period for IPv6 deployment. What is the estimate for small and large sized organization? </pre> </blockquote> <pre wrap=""> We're working on it since about 13 years... </pre> <blockquote type="cite"> <pre wrap="">Are the transition mechanisms the same for these organizations? </pre> </blockquote> <pre wrap=""> Which transition mechanisms make sense are very much different depending on the organization type, network structure, existing hardware, and on the *goals* to be reached (as in "have IPv6 everywhere" or "enable IPv6 at some key network elements, e.g. the internet facing proxy"). For us, "dual-stack everywhere" is the way to go, but this will be very different for other organizations. Gert Doering -- NetMaster </pre> </blockquote> Hi, If I can help you we're starting to delivery ipv6 on our backbone (about 90 PE). Our infrastucture is mpls but the ipv6 mpls control plane isn't yet implemented by vendors so we chosen implement dual-stack on GRT followed by 6VPE (dual-stack) for vpn mpls. The plan to deploy was divided: 1) Planning 2) Upgrade backbone 3) Deploy Total time: 2 years for backbone Other problem is related to customers. We can't force to change or upgrade the end-point devices ($$!!) so the time delivery for customers will be longer. Isacco <pre class="moz-signature" cols="72">---------------------------------------------------------------------------------------------------------------------------</pre> </body> </html>