Re: [dnsop] Re: WGLC for draft-ietf-dnsop-bad-dns-res-02.txt

JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp> Tue, 29 June 2004 09:24 UTC

Received: from darkwing.uoregon.edu (darkwing.uoregon.edu [128.223.142.13]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05340 for <dnsop-archive@lists.ietf.org>; Tue, 29 Jun 2004 05:24:31 -0400 (EDT)
Received: from darkwing.uoregon.edu (localhost [127.0.0.1]) by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i5T7MRx5002896; Tue, 29 Jun 2004 00:22:27 -0700 (PDT)
Received: (from majordom@localhost) by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i5T7MROk002895; Tue, 29 Jun 2004 00:22:27 -0700 (PDT)
Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i5T7MQjS002810 for <dnsop@lists.uoregon.edu>; Tue, 29 Jun 2004 00:22:26 -0700 (PDT)
Received: from ocean.jinmei.org (unknown [3ffe:501:100f:1048:c8d3:831a:dc60:4268]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id DA17115263; Tue, 29 Jun 2004 16:22:24 +0900 (JST)
Date: Tue, 29 Jun 2004 16:22:35 +0900
Message-ID: <y7vzn6mltfo.wl@ocean.jinmei.org>
From: JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp>
To: dnsop@lists.uoregon.edu
Cc: mlarson@verisign.com, pbarber@verisign.com
Subject: Re: [dnsop] Re: WGLC for draft-ietf-dnsop-bad-dns-res-02.txt
In-Reply-To: <20040624200408.GA29798@1-4-5.net>
References: <20040624200408.GA29798@1-4-5.net>
User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0 (SAKAKI)
Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan.
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset="US-ASCII"
Sender: owner-dnsop@lists.uoregon.edu
Precedence: bulk
Reply-To: JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp>

(explicitly cc'ing to the authors)

>>>>> On Thu, 24 Jun 2004 13:04:08 -0700, 
>>>>> David Meyer <dmm@1-4-5.net> said:

> 	The WGLC on this one was scheduled to end today at 1500
> 	PDT (GMT/UTC-7). However, there have been several
> 	comments that need to be resolved before we can go
> 	forward. We will revisit this one after the authors have
> 	revised the document.

In section 2.2.1, the draft says:

   [...]
   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.  [...]

In general, I agree on this recommendation.  But it might cause a
rather undesirable result when all authoritative servers seem to be
lame, since some authoritative server implementations can be lame for
particular resource record types.  (See Section 4.4 of
draft-ietf-dnsop-misbehavior-against-aaaa-01.txt for more details)

Of course, what is wrong here is "lame" authoritative servers.  But
sometimes we need to explore workaround to deal with real-world's
problems...

Meanwhile, I'm not sure if the recommendation also applies to the case
where *all* authoritative servers seem to lame.  In the beginning of
Section 2.2, the draft says as follows:

   A more common occurrence is a subset of a zone's name servers being
   unavailable or misconfigured.

But I could not be sure if this section (including the recommendation)
only concentrates on the case where a subset of the servers behave
badly or it also considers the case where all of them are bad.

If the intention is the former, then please make it clear throughout
the section, particularly in Section 2.2.1.

If the intention is the latter, I hope the document also notes that
the recommended behavior may sometimes cause undesirable result while
the behavior generally makes sense.

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp
.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html