[ipv6hackers] subject labels

[Douglas Otis]

On 11/30/11 8:22 PM, Richard Barnes wrote:
>  Well, there are some people thinking about the problem
> 
<http://tools.ietf.org/html/draft-ietf-v6ops-ipv6-multihoming-without-ipv6nat-03>
>
>  There's even an RFC
>  <http://tools.ietf.org/html/rfc6296>

i.e. DHCPv6 based assignments may need NPTv6 RFC6296.

A likely case for a NAT would be NAT64 defined in RFC6144, RFC6145, 
RFC6146, RFC6052, RFC6147, and RFC6384.  Multihoming has been a long 
standing feature of SCTP prominently used in cellular and multimedia 
communications where reliability and performance is essential.

http://tools.ietf.org/html/draft-garcia-shim6-applicability-02

There is also an interesting informational rfc regarding IPv6-only 
networks and the use of NAT64.  This points to incidents involving IPv4 
literals that require work-around approaches in less than %2 of the 
cases within IPv6 only networks.

http://tools.ietf.org/html/draft-arkko-ipv6-only-experience-04

Section 3.2 DNS Operation
,---
Router Advertisements are used to carry DNS Configuration options 
[RFC6106 <http://tools.ietf.org/html/rfc6106>], listing the DNS64 as the 
DNS server the hosts should use. In addition, aliases were added to the 
DNS64 device to allow it to receive packets on the well-known DNS server 
addresses that Windows operating systems use (fec0:0:0:ffff::1, 
fec0:0:0:ffff::2, and fec0:0:0:ffff::3).  At a later stage support for 
stateless DHCPv6 [RFC3736 <http://tools.ietf.org/html/rfc3736>] was 
added. We do recommend enabling RFC6106, well-known addresses, and 
stateless DHCPv6 in order to maximize the likelihood of different types 
of IPv6-only hosts being able to use DNS without manual configuration. 
DNS server discovery was never a problem in dual-stack networks, because 
DNS servers on the IPv4 side can easily provide IPv6 information (AAAA 
records) as well. With IPv6-only networking, it becomes crucial that the 
local DNS server can be reached via IPv6 as well.
'---

Other notes:
Mac OS X the network manager needed to be explicitly told to not expect 
IPv4. Windows 7 experienced problems when relying on default, well-known 
DNS server addresses: without manual configuration, the host was unable 
to use the DNS addresses, even though the system displays them as 
current DNS server addresses.

-Doug