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


        RFC 1966:

        Title:      BGP Route Reflection
                    An alternative to full mesh IBGP
        Author:     T. Bates & R. Chandra
        Date:       June 1996
        Mailbox:    tbates@cisco.com, rchandra@cisco.com
        Pages:      7
        Characters: 14,320
        Updates/Obsoletes: none

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


The Border Gateway Protocol is an inter-autonomous system routing
protocol designed for TCP/IP internets. BGP deployments are configured
such that that all BGP speakers within a single AS must be fully
meshed so that any external routing information must be re-distributed
to all other routers within that AS. This represents a serious scaling
problem that has been well documented with several alternatives
proposed.  This document describes the use and design of a method
known as "Route Reflection" to alleviate the the need for "full mesh"
IBGP.  This RFC is the product of the Inter-Domain Routing Working
Group of the IETF.

This memo defines an Experimental Protocol for the Internet community.
This memo does not specify an Internet standard of any kind.
Discussion and suggestions for improvement are requested.
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