Bill Manning wrote:
On Dec 7, 2004, at 7:44, Brian E Carpenter wrote:
Bill Manning wrote:
On Dec 6, 2004, at 10:31, Brian E Carpenter wrote:
Dan Lanciani wrote:
Mark Andrews <[EMAIL PROTECTED]> wrote:
|+ Advertising locally assigned ULA AAAA records in the global
DNS is
|+ MUST NOT occur as they are not globally unique and will lead
|+ to unexpected connections.
I strongly object to making this a "MUST NOT," ...
OK. Lot of shouting since this was sent but not much new text.
How about
Locally assigned ULA AAAA records MUST NOT appear in the global
DNS,
since there is an extremely small probability that the
corresponding
addresses are not unique. Even though these addresses will be
unrouteable in the global Internet, their leakage via DNS is highly
undesirable. Such AAAA records MAY appear in local regions of
the DNS
corresponding to their region of routeability.
keep your mitts off my zone files.
and if the prefixes are routable -AT ALL- then i may chose to
define my "local region" to be the Internet.
Bill, you could do that if the prefixes are *routed* but that is
not going to be the case if the ULA spec is followed, except for
private routing arrangements. Since the spec says they MUST NOT
be globally routed, it seems entirely rational to apply the same
rule to your zone files. But as I said before, I can live with
SHOULD NOT.
Brian
please define "globally routable" in technical terms.
Why? I didn't use that phrase. The draft doesn't say that, it says
that ULA prefixes must not be globally routed. Different.
and since routing is not the same as lookup, your assertion
about the "rational" nature of registration in a lookup system
does not hold much credence.
Not at all. As others have pointed out, if DNS returns AAA records
for prefixes that are not in fact routed, TCP timeouts will result.
That's sufficient reason to not put such records in your zone files.
Brian
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[EMAIL PROTECTED]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------