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


        RFC 1932:

        Title:      IP over ATM: A Framework Document
        Author:     R. Cole, D. Shur, & C. Villamizar
        Date:       April 1996
        Mailbox:    rgc@qsun.att.com, d.shur@att.com, curtis@ans.net
        Pages:      31
        Characters: 68,031
        Updates/Obsoletes:  none

        URL:        ftp://ds.internic.net/rfc/rfc1932.txt


The discussions of the IP over ATM working group over the last several
years have produced a diverse set of proposals, some of which are no
longer under active consideration.  A categorization is provided for
the purpose of focusing discussion on the various proposals for IP
over ATM deemed of primary interest by the IP over ATM working group.
The intent of this framework is to help clarify the differences
between proposals and identify common features in order to promote
convergence to a smaller and more mutually compatible set of
standards.  In summary, it is hoped that this document, in classifying
ATM approaches and issues will help to focus the IP over ATM working
group's direction.  This RFC is the product of the IP Over
Asynchronous Transfer Mode 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-DIST-REQUEST@ISI.EDU.

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