A few thoughts: IPv6 hosts generally cannot contact IPv4 hosts, and vice versa. There are several exceptions, one being dual-stacked hosts - machines with both IPv4 and IPv6 connectivity. Unless you're going to set up a new Exchange server specifically for this MPLS network - an Exchange server that won't be able to talk to anyone else - you're going to need to start implementing IPv6 company-wide.
Perform due diligence! Microsoft's products most likely won't be an issue, especially if you're using the latest & greatest. I can't say the same for niche products, like your point-of-sale software and/or hardware... In the highly likely event you don't have an IPv6 allocation from your ISP, ICANN, ARIN, APNIC, RIPE - or whoever the appropriate body would be for your organization - you should make sure you're using a ULA prefix (Unique Local Address: http://en.wikipedia.org/wiki/Unique_local_address; http://tools.ietf.org/html/rfc4193). In IPv6, the ULA address space is roughly equivalent to the RFC1918 subnets (aka 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16). The site-local prefix fec0::/10 was depreciated by RFC3879. Other references: IPv6 ULA prefix generator: http://www.simpledns.com/private-ipv6.aspx Cisco documentation on IPv6 in VoIP networks: http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/ipv6/ipv6srnd.html RFC3879: http://www.faqs.org/rfcs/rfc3879.html On 6/17/2010 12:31 AM, Ryan Finnesey wrote: > I have somewhat of an off topic question. Has anyone deployed services > on a completely IPv6 network? We need to deploy a new MPLS network to > about 320 locations and I was thinking of using IPv6 for the internal > network. The services we need to run are VoIP(Cisco) and the core > Microsoft Apps SQL Exchange, SharePoint BizTalk) and Micros for POS. -- Phil Brutsche [email protected] ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
