[Disman] FW: draft-ietf-disman-remops-mib-v2-09.txt
"Wijnen, Bert (Bert)" <bwijnen@lucent.com> Fri, 10 March 2006 14:32 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FHifI-0004Ug-Jb; Fri, 10 Mar 2006 09:32:24 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FHifG-0004Ts-IM for disman@ietf.org; Fri, 10 Mar 2006 09:32:22 -0500
Received: from ihemail1.lucent.com ([192.11.222.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FHifG-0000D0-9W for disman@ietf.org; Fri, 10 Mar 2006 09:32:22 -0500
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id k2AEWJTv000778; Fri, 10 Mar 2006 08:32:20 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id <G3YWWQ0W>; Fri, 10 Mar 2006 15:32:18 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15509849086@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Disman (E-mail) (E-mail)" <disman@ietf.org>
Date: Fri, 10 Mar 2006 15:32:15 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Cc: "David Kessens (E-mail)" <david.kessens@nokia.com>, "Pekka Savola (E-mail)" <pekkas@netcore.fi>
Subject: [Disman] FW: draft-ietf-disman-remops-mib-v2-09.txt
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
FYI and follow up. I have not looked at this in detail yet (may not get to it untill Tuesday next week). So forwarding to WG for review/comment/response. Bert -----Original Message----- From: owner-ops-dir@ops.ietf.org [mailto:owner-ops-dir@ops.ietf.org]On Behalf Of Pekka Savola Sent: Friday, March 10, 2006 11:23 To: Ops Directorate Subject: draft-ietf-disman-remops-mib-v2-09.txt On Thu, 9 Mar 2006, David Kessens wrote: ... I don't usually look at MIB modules, but did take a peek at draft-ietf-disman-remops-mib-v2-09.txt. A couple of comments below. Substantial ----------- 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. 2) In lookupCtlTargetAddressType (for example), the user is required to specify whether the address in IP->name conversion is IPv4 or IPv6 address. This is unfortunate; you should not need to specify that, as the lookup functions are able to figure it out on their own. You should be able to give also 'ip' which would do v4 lookup if the address is v4 or v6 lookup if the address is v6, as appropriate. 3) The specification includes a lot of 'getaddrinfo() or gethostbyname()' and 'getnameinfo() or gethostbyaddr()', but the latter functions do not support IPv6. Is there any reason to mention those at all, because you can't implement this MIB mobule (so that it could support v6) just by using gethostbyname/gethostbyaddr? I'd suggest just mentioning getaddrinfo/getnameinfo(). Editorial --------- ==> usually (not sure about MIB modules), differences to the previous RFC are listed in the draft, maybe in an appendix. This information is mostly available in the draft, but it's scattered in 3 places. Not sure if it'd make sense to sum it up. traceRouteCtlPort OBJECT-TYPE SYNTAX Unsigned32 (1..65535) UNITS "UDP Port" MAX-ACCESS read-create STATUS current DESCRIPTION "Specifies the UDP port to send the traceroute request to. Need to specify a port that is not in use at the destination (target) host. The default value for this object is the IANA assigned port, 33434, for the traceroute function." DEFVAL { 33434 } ::= { traceRouteCtlEntry 9 } ==> actually, most implementations use the UDP port number for the _first_ traceroute they send, incrementing the port number for next messages, so that you can distinguish which hop the replies came from. So, the text may require a minor tweak. -- 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