RFC 2918 (rfc2918) - Page 3 of 4

Route Refresh Capability for BGP-4

RFC 2918                Route Refresh for BGP-4           September 2000


   If a BGP speaker receives from its peer a ROUTE-REFRESH message with
   the  that the speaker didn't advertise to the peer at the
   session establishment time via capability advertisement, the speaker
   shall ignore such a message.  Otherwise, the BGP speaker shall re-
   advertise to that peer the Adj-RIB-Out of the  carried in
   the message, based on its outbound route filtering policy.

5. Security Considerations

   This extension to BGP does not change the underlying security issues.

6. Acknowledgments

   The concept of Route Refresh proposed is similar to the one used in
   IDRP.

   The author would like to thank Yakov Rekhter, Ravi Chandra, Srihari
   Ramachandra and Bruce Cole for their review and comments.

7. References

   [BGP-4]   Rekhter, Y. and T. Li, "A Border Gateway Protocol 4 (BGP-
             4)", RFC 1771, March 1995.

   [BGP-MP]  Bates, T., Chandra, R., Katz, D. and Y. Rekhter,
             "Multiprotocol Extensions for BGP-4", RFC 2858, June 2000.

   [BGP-CAP] Chandra, R. and J. Scudder, "Capabilities Advertisement
             with BGP-4", RFC 2842, May 2000.

8. Author's Address

   Enke Chen
   Redback Networks Inc.
   350 Holger Way
   San Jose, CA 95134

   EMail: enke@redback.com













Chen                        Standards Track