On Tue, 2 Aug 2005, Paul Vixie wrote:
the draft name is draft-ietf-dnsop-ipv6-dns-issues-11.txt for those who,
like me, try to use google to find its text.
sorry for mistyping from the memory.
i don't nec'ily consider the iesg an expert on this, so their approval
may or may not matter much. the current -respsize- draft describes what
a large part of the installed base of dns query initiators actually does.
the best thing would be to shorten -respsize- by removing anything it
does not absolutely HAVE to say.
That's certainly one option, though then it would give less
information to the readers. Personally, documents like this exist to
educate the community, and clarifying how the TC / additional data
processing works should help (as obviously different folks have
different notions of it). It doesn't necessarily have to be in this
document, though as topic being discussed is related, this could be at
least one logical place.
[...]
forgive my ignorance. i was describing behaviour i'm aware of. if rfc2181
says that, it's boneheaded, but we should follow it here (or at least remove
any text in -respsize- that conflicts with it) rather than argue about it.
[...]
==> as above, not having such "reflexes" would be against RFC2181
and yet, since the installed base actually works the way this -respsize-
draft describes, the issues that will affect choices of NS RRsets are
exactly as written, and rfc2181 is possibly-irrelevant. perhaps adding
a small editorial indicating this schism is the best fix overall?
Note that I sent a query about this on namedroppers a while ago,
asking for the implementors to report what they're doing. Below is
what Jinmei reported on recent versions of BIND, at least. (There
haven't been other reports.) Not sure if you were familiar with
earlier (4.x, more broken?) versions..
=========
3. if your implementation (or the implemenations you're familiar
with) receives a response with TC bit set and an additional
section, what does it do?
a) ignore everything in the response, and re-query using TCP.
b) keep some or all of the data in the response, re-query using
TCP (additional details would be welcome).
c) something else, what?
ISC BIND 9.3.1 a)
ISC BIND 8.4.6 a) (there seem to be some exceptional cases, but I
think we can ignore such cases in this discussion).
===============
--
Pekka Savola "You each name yourselves king, yet the
Netcore Oy kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html
