[rfc-dist] RFC 4560 on Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations

[rfc-editor@rfc-editor.org]

A new Request for Comments is now available in online RFC libraries.

        
        RFC 4560

        Title:      Definitions of Managed Objects for 
                    Remote Ping, Traceroute, and Lookup Operations 
        Author:     J. Quittek, Ed.,
                    K. White, Ed.
        Status:     Standards Track
        Date:       June 2006
        Mailbox:    quittek at netlab.nec.de, 
                    wkenneth at us.ibm.com
        Pages:      100
        Characters: 207956
        Obsoletes:  RFC2925
        See-Also:   

        I-D Tag:    draft-ietf-disman-remops-mib-v2-09.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4560.txt

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 they are 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.

Currently, there are several enterprise-specific MIBs for performing
remote ping or traceroute operations.  The purpose of this memo is to
define a standards-based solution to enable interoperability.  
[STANDARDS TRACK]

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

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and 
suggestions for improvements.Please refer to the current edition of 
the Internet Official Protocol Standards (STD 1) for the standardization 
state and status of this protocol.  Distribution of this memo is 
unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...