Revision as of 12:04, 26 August 2009 edit Mitar (talk \| contribs) Extended confirmed users 675 edits No edit summary ← Previous edit		Revision as of 16:04, 30 October 2009 edit undo David dolson (talk \| contribs) 2 edits mNo edit summary Next edit →
Line 2: '''IPv6 transition mechanisms''' are used to allow [[IPv6]]-connected hosts to access [[IPv4]]-only Internet resources and hosts. Some IPv6 transition mechanisms were first defined in RFC 1933 but this RFC has been obsoleted by RFC 4213. There exists an ongoing process for a IPv4/IPv6 translation framework as described in [http://www.viagenie.ca/ietf/draft/draft-baker-behave-v4v6-framework-02.txt draft-baker-behave-v4v6-framework]. It also explains the background of the problem and some expected uses. Another document describes the translation proposal [http://www.viagenie.ca/ietf/draft/draft-baker-behave-v4v6-translation-02.txt draft-baker-behave-v4v6-translation]. There are two concrete protocol proposals that have much in common: [http://www.viagenie.ca/ietf/draft/draft-bagnulo-behave-nat64-03.txt NAT64]/[http://www.viagenie.ca/ietf/draft/draft-bagnulo-behave-dns64-02.txt DNS64] and [http://www.viagenie.ca/ietf/draft/draft-baker-behave-ivi-01.txt IVI]. Also [http://tools.ietf.org/html/draft-~~durand~~ietf-softwire-dual-stack-lite-0002 Dual Stack Lite] has been proposed. There are also some implementations for proposed solutions:

IPv6 transition mechanism: Difference between revisions