RE: [Disman] FW: draft-ietf-disman-remops-mib-v2-09.txt

["Wijnen, Bert (Bert)" <[e-mail]>]

W.r.t.
> >> 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.
> >>
> >
> > The format is REQUIRED in order for the SNMP agent to be able to determine
> > (and validate) the content of the lookupCtlTargetAddress object itself.
> > So it is inherent in the use of these TCs, and not because it is
> > needed for underlying lookup functions.
> 
> But it would be possible to have a lookup type where the TC is 
> basically "any text string that is less than 50 characters in length?
> Because if you give an address to look up with 'nslookup', the 
> address is just an opaque text blob..
> 

Pekka, this may be true for how you pass the address to the underlying 
lookup function. But I think what you are after here does NOT belong
in the InetAddressType and InetAddress TCs (see RFC4001). So I would
strongly recommend to keep what we have. An implementation can choose
to just use the InetAddress value and pass that as is to the
underlying lookup functions which will then figure out what sort of
address it is. 

> >> 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().
> >>
> >
> > They are listed as "for example", so I think that that is OK.
> 
> I have to disagree with this because the example doesn't work. (On the 
> other hand, if the spec said, "getaddrinfo() or gethostbyname() and 
> gethostbyname2()", then I think it would be workable though 
> deprecated by the latest IPv6 API documents.
> 

I guess the examples are IPv4 examples, no? 
Does it not work for that either? 
If it does work for IPv4, then I think the examples are fine.
If not even that, then maybe a better example can be used instead.

Bert
> >> 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.
> >>
> >
> > Fine. Even so the initial value would be the one to start from, no?
> >
> > So I do not see a need to add text.
> 
> Certainly, but the problem is that the text doesn't say "initial", so 
> the above description could be interpreted to be normative, 
> i.e., "all 
> the traceroute probes must originate from this port number".
> 
> The minor clarification can easily be addressed by rewording:
> 
> >>             "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
> ...
> 
> to e.g.,:
> 
> >>             "Specifies the initial 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
> 
> 
> -- 
> Pekka Savola                 "You each name yourselves king, yet the
> Netcore Oy                    kingdom bleeds."
> Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
>