>>>>> On Sat, 04 Dec 2004 14:29:00 +0900,
>>>>> JINMEI Tatuya <[EMAIL PROTECTED]> said:
>> This is a working group last call on the "Observed DNS Resolution
>> Misbehavior" draft, draft-ietf-dnsop-bad-dns-res-03.txt, which we
>> hope to submit to the IESG for consideration as a BCP document.
>> This last call will terminate at 17:00 UTC on 6 December 2004.
>> Please clearly state to the mailing list whether you support or oppose
>> this draft going to the IESG.
>> Please do not express an opinion if you have not read the draft.
>> As always, please discuss substantive issues on the WG mailing list.
>> Minor editorial comments may be sent directly to the draft authors
>> (please CC the WG chairs on any such comments so that we can track
>> this).
> I think my concern to the previous last call (attached below) is still
> there. It's my bad that I've not sent a proposed text to address this
> that I promised before, but if you give me some more time, I'll make a
> suggestion and send it to the list next week.
Below is my proposed text to address my concern. I'd first like to
proposed an additional paragraph at the end of section 2.2. And then
I'd propose some changes in the paragraph of Section 2.2.1. In the
proposed text I assume we can refer to
draft-ietf-dnsop-misbehavior-against-aaaa-02.txt to provide background
information, but I believe we can also convey the same point without
the reference if we do not want to have an additional reference.
Thanks,
JINMEI, Tatuya
Communication Platform Lab.
Corporate R&D Center, Toshiba Corp.
[EMAIL PROTECTED]
2.2 Repeated queries to lame servers
[...]
It should also be noted, however, that some authoritative name
server behave as lame servers only for queries of some specific
types [x]. In this case, it makes sense to retry the "lame"
servers for other types of queries, particularly when all known
authoritative name servers seem to be "lame".
[x] draft-ietf-dnsop-misbehavior-against-aaaa-02.txt
2.2.1 Recommendation
Iterative resolvers SHOULD cache name servers that they discover are
not authoritative for zones delegated to them (i.e. lame servers).
Lame servers MUST be cached against the specific query tuple <zone
name, class, server IP address>. Zone name can be derived from the
owner name of the NS record that was referenced to query the name
server that was discovered to be lame. Implementations that perform
lame server caching MUST refrain from sending queries to known lame
servers based on a time interval from when the server is discovered
to be lame as long as the implementations know non-lame servers.
A minimum interval of thirty minutes is RECOMMENDED. However, it
still makes sense to keep trying the lame server when all servers
are seem to be lame as a last resort, in order to workaround the
type-specific lame servers described in the previous section.
.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html
