warrant, remove the old, which is now no longer necessary.
view, or is infeasible due to a shortage of global address space.
used to facilitate a long-term program of transition.
use in an algorithmic mapping.
about the reliability of peers from history or by reputation.
They use the long-term sessions to map content availability.
Both stateless and stateful solutions can support Scenario 1.
hosts as discussed in Section 7.3 of [RFC6147].
translator, and this technique was deprecated by the IETF [RFC4966].
viable for this scenario, and other techniques should be considered.
conclusions for Scenario 7 also apply for this scenario.
addresses (IPv4-converted addresses) in the IPv4-to-IPv6 direction.
will be different for stateless translation and stateful translation.
addresses are mapped into IPv6 and used by physical IPv6 nodes.
initiated as well as IPv4 initiated communications.
in general only supports IPv6-initiated communication.
is critical to the operation of the applications using it.
describes a mechanism for maintaining state.
scalability compared with stateful translation [RFC6145].
systems to open sessions with IPv4 systems [RFC6145] [RFC6146].
to an IPv4 network", and "an IPv6 network to an IPv4 network".
an IPv4 address, part of the SIIT update) [RFC6052].
part of the SIIT update) [RFC6145].
and mapping table handling) [RFC6146].
o  DNS64 (DNS64: A to AAAA mapping and DNSSEC discussion) [RFC6147].
o  Others (DNS46, Multicast, etc.).
Format, IP/ICMP Translation, and Table Maintenance documents.
network.  We obviously recommend the latter at the present stage.
For the IPv4 parts of the network, [RFC4213]'s recommendation holds.
approach to transition entails the least risk.
Philip Matthews, Remi Denis-Courmont, and Remi Despres.
[6NET]     6NET Consortium, "6NET", <http://www.6net.org/>.
Exhaustion", Work in Progress, March 2011.