DUAL STACK (http://tools.ietf.

org/html/rfc4213#page-4
)
A Dual Stack is basically used to run two IP versions on the same
interface. Dual Stack is a technique used for the IPv6 integration,
(Hagen 2006) (PLANNING FOR IPV6). Therefore, for such applications
that cannot be upgraded to support IPv6, it can coexist with the
upgraded applications by using Dual Stack technique on the same
end system (IPv6IntegrationandCoexistenceStrategiesforNextGenerationNetworks).
The direct way for IPv6 nodes keeps compatible with IPv4 only
nodes is by doing a whole Ipv4 implementation. Therefore the IPv6
and IPv4 nodes can send a receive packets because they
interoperate directly with IPv4 and IPv6 packets.
A node is equipped to support both protocol, however it can disable
one or the other. In other words, it can operate using one of these
modes:
IPv4 enabled and IPv6 disabled
IPv6 enabled and IPv4 disabled
IPv4 and IPv6 enabled.
Address Configuration
Due to the nodes support IPv4 and IPv6, nodes can be configured
with their respective addresses. In other hand, IPv6/IPv4 nodes use
DHCP to obtain IPV4 addresses while In IPv6 obtains it addresses
automatically or by using DHCPv6.
DNS
Domain Name System (DNS) is used to map hostnames and IP
addresses of both IP protocol. Due to IPv6/IPv4 nodes are capable to
interoperate with both IP nodes, they should provide resolver
libraries able of dealing with "A" records of IPv4 and "AAAA" records
of IPv6.
Todo el resto fue sacado de (http://tools.ietf.org/html/rfc4213#page4)
https://tools.ietf.org/html/rfc4213
Joseph davies picture

http://www.cisco.com/c/dam/en/us/products/collateral/ios-nx-ossoftware/enterprise-ipv6-solution/aag_c45-625513.pdf

http://long.ccaba.upc.es/long/045Guidelines/key_issues.html

http://www.cybertelecom.org/dns/ipv6_transition.htm

https://www.us.ntt.net/assets/gr_ipv6_tunneling.jpg
ISSUES :

Benefits:
Can be deployed on hosts, routers, on same interface as IPv4
?Deals with most address selection and DNS resolution issues
?Allows hosts to continue to reach IPv4 resources, while also adding IPv6 functionality
?Simple to deploy. Allows backwards compatibility (IPv4 support)
?Available on most platforms. Easy to use, flexible.

Issues:

?May require 2 routing tables & routing processes

?Additional CPU, memory
?IPv6 network security requirements are same as IPv4 networks today dont overlook
enforcing security on parallel protocol

Application Deployment:
nd

?Easy way to deploy, flexible, bring up 2 protocol in parallel with first

The network bandwidth is shared and its use prioritized between

the two protocols. In most cases total traffic does not increase
substantially, but some capacity planning might be a good idea,
especially if you are adding new IPv6 services to your network.
Hosts need resources for two independent TCP/IP stacks.
You may need two IGP routing protocols.
Routers share resources for holding routing information and
performing SP (shortest path) calculations and lookups for each
protocol.
You need two security concepts. Security requirements and
administration will be different for IPv4 and IPv6.
Security devices need more resources for handling two protocol
versions. Hardware forwarding devices, for example, support a
limited number of ACLs, which could be too limited to handle ACLs
for IPv6 in addition to the IPv4 ACLs.
Operational and management tools must support two protocols in
provisioning, monitoring, and troubleshooting.
In spite of these complications, the advantages you get from the
flexibility a dual-stack approach offers probably outweigh the
disadvantages.
Excerpt From: Hagen, Silvia. Planning for IPv6. iBooks.
Excerpt From: Hagen, Silvia. Planning for IPv6. iBooks.