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


        RFC 1937:

        Title:      "Local/Remote" Forwarding Decision in Switched
                    Data Link Subnetworks
        Author:     Y. Rekhter & D. Kandlur
        Date:       May 1996
        Mailbox:    yakov@cisco.com, kandlur@watson.ibm.com
        Pages:      8
        Characters: 18,302
        Updates/Obsoletes:  none

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


The IP architecture assumes that each Data Link subnetwork is labeled
with a single IP subnet number. A pair of hosts with the same subnet
number communicate directly (with no routers); a pair of hosts with
different subnet numbers always communicate through one or more
routers. As indicated in RFC1620, these assumptions may be too
restrictive for large data networks, and specifically for networks
based on switched virtual circuit (SVC) based technologies (e.g. ATM,
Frame Relay, X.25), as these assumptions impose constraints on
communication among hosts and routers through a network.  The
restrictions may preclude full utilization of the capabilities
provided by the underlying SVC-based Data Link subnetwork.  This
document describes extensions to the IP architecture that relaxes
these constraints, thus enabling the full utilization of the services
provided by SVC-based Data Link subnetworks.  This RFC is the product
of the Routing over Large Clouds 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