Subject: Protocol Action: 'Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations' to Proposed Standard

From: The IESG <[email-masked]>
Date: Thu, 23 Mar 2006 10:08:46 -0500

The IESG has approved the following document:

- 'Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup 
   Operations '
   <draft-ietf-disman-remops-mib-v2-09.txt> as a Proposed Standard

This document is the product of the Distributed Management Working Group. 

The IESG contact persons are Bert Wijnen and David Kessens.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-disman-remops-mib-v2-09.txt

Technical Summary
 
   This memo defines Management Information Bases (MIBs) for performing
   ping, traceroute and lookup operations at a host.  When managing a
   network it is useful to be able to initiate and retrieve the results
   of ping or traceroute operations when performed at a remote host.  A
   Lookup capability is defined in order to enable resolution of either
   an IP address to an DNS name or a DNS name to an IP address at a
   remote host.

Working Group Summary
 
  There is WG consensus to publish this document as a Proposed Standard
  and thereby obsoleting RFC2925.

Protocol Quality
 
  This document has been reviewed by Juergen Schoenwaelder.
  Bert Wijnen reviewed this document for the IESG.

Note to RFC Editor
 
OLD:
1.3.  Lookup

   The Lookup operation enables remote lookup of addresses for a
   symbolic name as it is, for example, performed by functions
   getnameinfo() or gethostbyaddr() and lookup of symbolic names for a
   addresses as it is, for example, performed by functions getaddrinfo()
   or gethostbyname().  The lookup capability can be used to determine
   the symbolic name of a hop in a traceroute path.

NEW:
1.3.  Lookup

   The Lookup operation enables remote lookup of addresses for a
   symbolic name as it is, for example, performed by functions
   getnameinfo() or gethostbyaddr() and lookup of symbolic names for a
   addresses as it is, for example, performed by functions getaddrinfo()
   or gethostbyname().  Note that whatever lookup function is chosen,
   results are not necessarily consistent with the results of a pure
   Domain Name Service (DNS) lookup, but may be influenced by local
   lookup tables or other sources of information.  The lookup capability
   can be used to determine the symbolic name of a hop in a traceroute
   path.  Also the reverse lookup can be used, for example, for analyzing
   name lookup problems.

OLD:
3.1.4.  pingProbeHistoryTable

   The results of past ping probes can be stored in this table on a per
   pingCtlEntry basis.  This table is initially indexed by

NEW:
3.1.4.  pingProbeHistoryTable

   The results of each past ping probe are stored in this table on a per
   pingCtlEntry basis.  This table is initially indexed by

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 sources of information, depending on the configuration of
   the managed node.

   The lookupResultsTable is initially indexed by the same

On page 26
OLD:
    pingResultsTable OBJECT-TYPE
       SYNTAX      SEQUENCE OF PingResultsEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "Defines the Ping Results Table for providing
           the capability of performing ping operations at
           a remote host.  The results of these operations are
           stored in the pingResultsTable and the pingPastProbeTable.

NEW:
    pingResultsTable OBJECT-TYPE
       SYNTAX      SEQUENCE OF PingResultsEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "Defines the Ping Results Table for providing
           the capability of performing ping operations at
           a remote host.  The results of these operations are
           stored in the pingResultsTable and the pingProbeHistoryTable.

on page 51
OLD:
OLD:
      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."

NEW:
      traceRouteCtlPort OBJECT-TYPE
         SYNTAX      Unsigned32 (1..65535)
         UNITS       "UDP Port"
         MAX-ACCESS  read-create
         STATUS      current
         DESCRIPTION
             "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
             value for this object is the IANA assigned port,
             33434, for the traceroute function."

- on page 65:
OLD:
    traceRouteHopsHopIndex OBJECT-TYPE
       SYNTAX      Unsigned32 (1..'ffffffff'h)
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "Specifies the hop index for a traceroute hop.  Values
           for this object with respect to the same
           traceRouteCtlOwnerIndex and traceRouteCtlTestName
           MUST start at 1 and increase monotonically.

NEW:
    traceRouteHopsHopIndex OBJECT-TYPE
       SYNTAX      Unsigned32 (1..'ffffffff'h)
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "Specifies the hop index for a traceroute hop.  Values
           for this object with respect to the same
           traceRouteCtlOwnerIndex and traceRouteCtlTestName
           MUST start at 1, and be given increasing  values for
           subsequent hops.  The value of traceRouteHopsHopIndex
           is not necessarily the number of the hop on the traced path.

_______________________________________________
IETF-Announce mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/ietf-announce