said by tubbynet:said by dvd536:How many things this is going to break.
i am not sure what you're getting at.
many service providers have already been thinking about the ipv6 transition (and many have ipv6 functionality in the core). the issue is that there are many major manufacturers that don't *fully* support ipv6 in the same way that ipv4 is supported. service providers (especially those of small mpls-based networks) often implement "non-standard" solutions in order to provide value-added services to their customers. in doing so, they implement route-leaking, vrf importation, security measures, etc that aren't supported fully in ipv6, or its not supported *in hardware* (meaning the ipv6 packets must be punted to the supervisor/route-processor for software handling, rather than being able to be switching using something similar to cisco express forwarding (cef) in hardware).
as i see it, comcast makes no mention of going "fully ipv6" in the core, but offering ipv6 to the customer endpoints via dhcpv6 and then providing a typical 6-to-4 tunnel at some point before it hits the core - allowing existing infrastructure to be used.
will this affect a few things - sure. cpe has to support ipv6. comcast has to work out the bugs on each of their respective markets to make sure that everything works as promised. this is the point of a "trial". its not like their going cold-turkey.
q.
Excellent points.
