On Dec 7, 2004, at 1:23 PM, Bob Hinden wrote:
While I am sure everyone in this discussion has read the DNS text in the current draft, here it is just in case:
4.4 DNS Issues
At the present time AAAA and PTR records for locally assigned local
IPv6 addresses are not recommended to be installed in the global DNS.
The operational issues relating to this are beyond the scope of this
document.
For background on this recommendation, the concern about adding AAAA
and PTR records to the global DNS for locally assigned local IPv6
addresses stems from the lack of complete assurance that the prefixes
are unique. There is a small possibility that the same PTR record
might be registered by two different organizations. Due to this
concern, adding AAAA records is thought to be unwise because matching
PTR records can not be registered.
Bob,
This is unfortunately not the only concern. Actually, i would even say this is
a somehow minor issue, as the risk of collision is small.
The real concern is similar to what is explain in the v6ops IPv6onbydefault draft.
Say that a well know host publish 2 AAAA in the global DNS, a 'regular' one
and a ULA one, apparently to make local things works better.
What is going to happen is that remote hosts have statistically 50% chance
to try the ULA first. Then, if TCP is in used, an application will
have to wait up to 3 minutes (according to present TCP specs) before
it can safely fall back to the 2nd address. Note that some implementations
I know have lowered this timeout, but this is still a critical issue.
In other words, the concern is not so much with publishing local addresses
in a local branch of the DNS, but to publish both local and global
data for the same name.
- Alain.
-------------------------------------------------------------------- IETF IPv6 working group mailing list [EMAIL PROTECTED] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
