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


        RFC 1656:

        Title:      BGP-4 Protocol Document Roadmap and Implementation
                    Experience 
        Author:     P. Traina
        Mailbox:    pst@cisco.com
        Pages:      4
        Characters: 7,705
        Updates/Obsoletes:  none


Border Gateway Protocol v4 (BGP-4) is an inter-Autonomous System
routing protocol.  It is built on experience gained with BGP as
defined in RFC 1267 and BGP usage in the connected Internet as
described in RFC 1268.  BGP-4 provides a new set of mechanisms for
supporting classless inter-domain 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.  The
management information base has been defined and security
considerations are discussed in the protocol definition document.
This RFC is a product of the Border Gateway Protocol 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-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