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


        RFC 1574:

        Title:      Essential Tools for the OSI Internet
        Author:     S. Hares & C. Wittbrodt
        Mailbox:    skh@merit.edu, cjw@magnolia.Stanford.EDU
        Pages:      13
        Characters: 27,735
        Obsoletes:  1139


This memo specifies the following three necessary tools to debug
problems in the deployment and maintenance of networks using ISO 8473
(CLNP):

	- ping or OSI Echo function
	- traceroute function which uses the OSI Echo function
	- routing table dump function

These CLNS tools are the basics required for hosts and routers for
CLNS network support. It is intended that this document specify the
most basic support level required for CLNS hosts and routers.  To
support some of the needed tools (ping and traceroute), this memo
specifies the mechanism specified in RFC 1575.  This document is the
product of the Network OSI Operations Working Group of the IETF.

This memo provides information for the Internet community.  This memo
does not specify an Internet standard of any kind.  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@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        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 admin@DS.INTERNIC.NET.  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@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds
USC/Information Sciences Institute