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


        RFC 1654:

        Title:      A Border Gateway Protocol 4 (BGP-4)
        Author:     Y. Rekhter & T. Li, Editors
        Mailbox:    yakov@watson.ibm.com, tli@cisco.com
        Pages:      56
        Characters: 130,118
        Updates/Obsoletes:  none


The Border Gateway Protocol (BGP) is an inter-Autonomous System
routing protocol.  It is built on experience gained with EGP as
defined in RFC 904 and EGP usage in the NSFNET Backbone as described
in RFC 1092 and RFC 1093.  BGP-4 provides a new set of mechanisms for
supporting classless interdomain routing.  These mechanisms include
support for advertising an IP prefix and eliminates the concept of
network "class" within BGP.  BGP-4 also introduces mechanisms which
allow aggregation of routes, including aggregation of AS paths.  These
changes provide support for the proposed supernetting scheme.  This
RFC is a product of the Border Gateway Protocol Working Group of the
IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements.  Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) 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 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