RE: [Disman] FW: draft-ietf-disman-remops-mib-v2-09.txt
Pekka Savola <pekkas@netcore.fi> Wed, 15 March 2006 07:47 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FJQj0-0007jB-TN; Wed, 15 Mar 2006 02:47:18 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FJQiz-0007j0-SE for disman@ietf.org; Wed, 15 Mar 2006 02:47:17 -0500
Received: from netcore.fi ([193.94.160.1]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FJQiz-00070a-Dr for disman@ietf.org; Wed, 15 Mar 2006 02:47:17 -0500
Received: from netcore.fi (localhost [127.0.0.1]) by netcore.fi (8.12.8/8.12.8) with ESMTP id k2F7lDHa032371; Wed, 15 Mar 2006 09:47:13 +0200
Received: from localhost (pekkas@localhost) by netcore.fi (8.12.8/8.12.8/Submit) with ESMTP id k2F7l8ZT032368; Wed, 15 Mar 2006 09:47:09 +0200
Date: Wed, 15 Mar 2006 09:47:08 +0200
From: Pekka Savola <pekkas@netcore.fi>
To: Juergen Quittek <quittek@netlab.nec.de>
Subject: RE: [Disman] FW: draft-ietf-disman-remops-mib-v2-09.txt
In-Reply-To: <44C6C5FDB2C2EAB56C6BDAE4@[192.168.1.128]>
Message-ID: <Pine.LNX.4.64.0603150945230.32245@netcore.fi>
References: <7D5D48D2CAA3D84C813F5B154F43B155098492B2@nl0006exch001u.nl.lucent.com> <Pine.LNX.4.64.0603131001220.14000@netcore.fi> <44C6C5FDB2C2EAB56C6BDAE4@[192.168.1.128]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Virus-Scanned: ClamAV 0.88/1332/Wed Mar 15 00:22:52 2006 on otso.netcore.fi
X-Virus-Status: Clean
X-Spam-Status: No, score=-3.7 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on otso.netcore.fi
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>, "David Kessens (E-mail)" <david.kessens@nokia.com>, "Disman (E-mail) (E-mail)" <disman@ietf.org>
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>, <mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>, <mailto:disman-request@ietf.org?subject=subscribe>
Errors-To: disman-bounces@ietf.org
On Wed, 15 Mar 2006, Juergen Quittek wrote: >>>> I have a number of concerns about NSLOOKUP part of the MIB mobule. >>>> >>>> 1) It's not clear whether the host, given e.g., 'dns' as a lookup >>>> type, is only supposed to make a DNS lookup (which is what 'nslookup' >>>> does), or also consult /etc/hosts or equivalent (also possibly NIS or >>>> other similar directories as specified by /etc/nsswitch.conf or >>>> equivalent) if appropriate. >>> >>> Possibly that could be clarified somewhat. I think it is an implementation >>> matter (the way I interpret it), but even that could be stated. >>> If WG chair and author/editor agree, pls sens a proposed piece of text >>> that I can tell RFC-Editor to add. >> >> Agreed. I don't think this is a major issue itself, but if the intent is >> to give consistent results across implementations, some things need to be >> said about this. > > Would you be fine with the change I proposed in a message to Joel Halpern: > > OLD: > 3.3.3. lookupResultsTable > > The lookupResultsTable is used to store the results of lookup > operations. The lookupResultsTable is initially indexed by the same > > NEW: > 3.3.3. lookupResultsTable > > The lookupResultsTable is used to store the results of lookup > operations. Results to be reported here SHOULD be results of > a lookup function that is commonly used by applications at the > managed node. This implies that results are not necessarily > consistent with the results of a pure DNS lookup at the > managed node, but may be influenced by local lookup tables or > other source of information, depending on the configuration of > the managed node. > > The lookupResultsTable is initially indexed by the same Yes, looks excellent. (FWIW, I think I've been convinced now the NSLOOKUP TC problem is something that needs to be addressed on a different forum, and the current approach seems good enough for now.) -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
- [Disman] FW: draft-ietf-disman-remops-mib-v2-09.t… Wijnen, Bert (Bert)
- RE: [Disman] FW: draft-ietf-disman-remops-mib-v2-… Wijnen, Bert (Bert)
- RE: [Disman] FW: draft-ietf-disman-remops-mib-v2-… Pekka Savola
- RE: [Disman] FW: draft-ietf-disman-remops-mib-v2-… Wijnen, Bert (Bert)
- RE: [Disman] FW: draft-ietf-disman-remops-mib-v2-… Pekka Savola
- Re: [Disman] FW: draft-ietf-disman-remops-mib-v2-… Juergen Schoenwaelder
- RE: [Disman] FW: draft-ietf-disman-remops-mib-v2-… Juergen Quittek
- RE: [Disman] FW: draft-ietf-disman-remops-mib-v2-… Juergen Quittek
- RE: [Disman] FW: draft-ietf-disman-remops-mib-v2-… Pekka Savola