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


        RFC 1482:

        Title:      Aggregation Support in the NSFNET Policy-Based
		    Routing Database
        Author:     Mark Knopper & Steven J. Richardson
        Mailbox:    mak@merit.edu
        Pages:      11
        Characters: 25,330
        Updates/Obsoletes:  none

This document describes plans for support of route aggregation, as
specified in the descriptions of Classless Inter-Domain Routing (CIDR)
and the BGP-4 protocol, by the NSFNET Backbone Network Service.
Mechanisms for exchange of route aggregates between the backbone
service and regional/midlevel networks are specified.  Additionally,
the memo proposes the implementation of an Aggregate Registry which
can be used by network service providers to share information about
the use of aggregation.  Finally, the operational impact of
incorporating CIDR and aggregation is considered, including an
analysis of how routing table size will be affected.  This impact
analysis will be used to modify the deployment plan, if necessary, to
maximize operational stability.

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 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