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


        RFC 1520:

        Title:      Exchanging Routing Information Across Provider
                    Boundaries in the CIDR Environment
        Author:     Y. Rekhter & C. Topolcic
        Mailbox:    yakov@watson.ibm.com, topolcic@CNRI.Reston.VA.US
        Pages:      9
        Characters: 20,389
        Updates/Obsoletes:  none


The purpose of this memo is twofold.  First, it describes various
alternatives for exchanging inter-domain routing information across
domain boundaries, where one of the peering domain is CIDR-capable and
another is not.  Second, it addresses the implications of running
CIDR-capable inter-domain routing protocols (e.g., BGP-4, IDRP) on
intra-domain routing.  This document is not intended to cover all the
cases (either real or imaginable).  Rather, it focuses on what are
viewed to be the most common cases.  We expect that individual service
providers will use this document as guidelines in establishing their
specific operational plans for the transition to CIDR.

This memo provides information for the Internet community.  It does
not specify an Internet standard.  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 1111, "Instructions to RFC
Authors", for further information.


Joyce K. Reynolds
USC/Information Sciences Institute