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


        RFC 1716:

        Title:      Towards Requirements for IP Routers
        Author:     P. Almquist, Author
                    F. Kastenholz, Editor
        Mailbox:    kasten@ftp.com
        Pages:      186
        Characters: 432,330
        Updates/Obsoletes:  none


This document is a snapshot of the work of the Router Requirements
working group as of November 1991.  At that time, the working group
had essentially finished its task.  There were some final technical
matters to be nailed down, and a great deal of editing needed to be
done in order to get the document ready for publication.
Unfortunately, these tasks were never completed.  At the request of
the IETF Internet Area Director, the current editor took the last
draft of the document and, after consulting the mailing list archives,
meeting minutes, notes, and other members of the working group, edited
the document to its current form.

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