Re: Remops Implementation Survey

"Randy Presuhn" <[email protected]>
Newsgroups gmane.ietf.disman
Message-ID <009501c4531c$6f481080$7f1afea9@oemcomputer>
Hi -

Two months have gone by, and I've seen no response, nor have I seen
any response to Juergen Quittek's call for implementation results last
November.  Should we abandon our attempt to update the document?

Randy

> From: "Randy Presuhn" <[email protected]>
> To: "Disman (E-mail)" <[email protected]>
> Sent: Monday, April 05, 2004 12:25 PM
> Subject: [Disman] Remops Implementation Survey
>

> Hi -
>
> Here is the Implementation Survey for RFC 2925, the Remote Operations MIBs.
> Please send responses to [email protected] , or, if you would like your implementation
> to remain anonymous for the implementation report, to the WG chair at
> [email protected].
>
> =================================================
>
> Implementation Survey for RFC 2925,
> Definitions of Managed Objects for Remote Ping,
> Traceroute, and Lookup Operations
>
>
> Module: DISMAN-PING-MIB
> Implementation Source:
> Management Application / Agent:
>
>
> GROUPs:
> pingGroup (y/n): _
> pingNotificationsGroup (y/n): _
> pingTimeStampGroup (y/n): _
>
> OBJECTs:
> pingMaxConcurrentRequests (rw/ro): __
> pingCtlStorageType (rw/ro): __
> pingCtlType (rw/ro): __
> pingCtlByPassRouteTable (rw/ro): __
> pingCtlSourceAddressType (rw/ro): __
>             unknown (y/n): _
>             ipv4 (y/n): _
>             ipv6 (y/n): _
>
> pingCtlSourceAddress (rw/ro): __
> pingCtlIfIndex (rw/ro): __
> pingCtlDSField (rw/ro): __
> pingResultsIpTargetAddressType:
>             unknown (y/n): _
>             ipv4 (y/n): _
>             ipv6: _
> pingResultsIpTargetAddress:
>      0 (y/n): _
>      4 (y/n): _
>      16 (y/n): _
>
>
> Module: DISMAN-TRACEROUTE-MIB
> Implementation Source:
> Management Application / Agent:
>
> GROUPs:
> traceRouteGroup (y/n): _
> traceRouteTimeStampGroup (y/n): _
> traceRouteNotificationsGroup (y/n): _
> traceRouteHopsTableGroup (y/n):
>
> OBJECTs:
> traceRouteMaxConcurrentRequests (rw/ro): __
> traceRouteCtlByPassRouteTable (rw/ro): __
> traceRouteCtlSourceAddressType rw/ro): __
> traceRouteCtlSourceAddress (rw/ro): __
> traceRouteCtlIfIndex (rw/ro): __
> traceRouteCtlMiscOptions (rw/ro): __
> traceRouteCtlStorageType (rw/ro): __
> traceRouteCtlDSField (rw/ro): __
> traceRouteCtlType (rw/ro): __
> traceRouteResultsIpTgtAddrType
>         unknown (y/n): _
>         ipv4 (y/n): _
>         ipv6 (y/n): _
> traceRouteResultsIpTgtAddr
>         0 (y/n): _
>         4 (y/n): _
>         16 (y/n): _
> traceRouteProbeHistoryHAddrType
>         unknown (y/n): _
>         ipv4 (y/n): _
>         ipv6 (y/n): _
> traceRouteProbeHistoryHAddr
>         0 (y/n): _
>         4 (y/n): _
>         16 (y/n): _
> traceRouteHopsIpTgtAddressType
>         unknown (y/n): _
>         ipv4 (y/n): _
>         ipv6 (y/n): _
> traceRouteHopsIpTgtAddress
>         0 (y/n): _
>         4 (y/n): _
>         16 (y/n): _
>
>
> Module: DISMAN-NSLOOKUP-MIB
> Implementation Source:
> Management Application / Agent:
>
> GROUPs
> lookupGroup (y/n): _
>
> OBJECTs:
> lookupMaxConcurrentRequests (rw/ro): __
> lookupPurgeTime (rw/ro): __
>
>
> Deployment / Operational Experience:
>
>
> Comments:
>
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.