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


        RFC 1490:

        Title:      Multiprotocol Interconnect over Frame Relay     
        Author:     T. Bradley, C. Brown, & A. Malis
        Mailbox:    tbradley@wellfleet.com, cbrown@wellfleet.com,
                    malis_a@timeplex.com
        Pages:      35
        Characters: 75,206
        Obsoletes:  1294


This memo describes an encapsulation method for carrying network
interconnect traffic over a Frame Relay backbone.  It covers aspects
of both Bridging and Routing.  Additionally, it describes a simple
fragmentation procedure for carrying large frames over a frame relay
network with a smaller MTU.  Systems with the ability to transfer both
the encapsulation method described in this document, and others must
have a priori knowledge of which virtual circuits will carry which
encapsulation method and this encapsulation must only be used over
virtual circuits that have been explicitly configured for its use.
This RFC is a product of the IP over Large Public Data Networks
Working Group of the IETF.

This is now a Draft Standard Protocol.

This RFC specifies an IAB standards track protocol for the Internet
community, and requests discussion and suggestions for improvements.
Please refer to the current edition of the "IAB Official Protocol
Standards" 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@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 NIC.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 1111, "Instructions to RFC
Authors", for further information.


Joyce K. Reynolds
USC/Information Sciences Institute