Browse Prior Art Database

A Border Gateway Protocol 4 (BGP-4) (RFC1654)

IP.com Disclosure Number: IPCOM000002490D
Original Publication Date: 1994-Jul-01
Included in the Prior Art Database: 2019-Feb-12
Document File: 56 page(s) / 71K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

Y. Rekhter: AUTHOR [+1]

Related Documents

10.17487/RFC1654: DOI

Abstract

This document defines an inter-autonomous system routing protocol for the Internet. [STANDARDS-TRACK]

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 3% of the total text.

Network Working Group Y. Rekhter Request for Comments: 1654 T.J. Watson Research Center, IBM Corp. Category: Standards Track T. Li cisco Systems Editors July 1994

A Border Gateway Protocol 4 (BGP-4)

Status of this Memo

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.

1. Acknowledgements

This document was originally published as RFC 1267 in October 1991, jointly authored by Kirk Lougheed (cisco Systems) and Yakov Rekhter (IBM).

We would like to express our thanks to Guy Almes (Rice University), Len Bosack (cisco Systems), and Jeffrey C. Honig (Cornell University) for their contributions to the earlier version of this document.

We like to explicitly thank Bob Braden (ISI) for the review of the earlier version of this document as well as his constructive and valuable comments.

We would also like to thank Bob Hinden, Director for Routing of the Internet Engineering Steering Group, and the team of reviewers he assembled to review the previous version (BGP-2) of this document. This team, consisting of Deborah Estrin, Milo Medin, John Moy, Radia Perlman, Martha Steenstrup, Mike St. Johns, and Paul Tsuchiya, acted with a strong combination of toughness, professionalism, and courtesy.

This updated version of the document is the product of the IETF BGP Working Group with Yakov Rekhter and Tony Li as editors. Certain sections of the document borrowed heavily from IDRP [7], which is the OSI counterpart of BGP. For this credit should be given to the ANSI X3S3.3 group chaired by Lyman Chapin (BBN) and to Charles Kunzinger (IBM Corp.) who was the IDRP editor within that group. We would also like to thank Mike Craren (Proteon, Inc.), Dimitry Haskin (Wellfleet), John Krawczyk (Wellfleet), and Paul Traina (cisco) for

Rekhter & Li [Page 1]

RFC 1654 BGP-4 July 1994

their insightful comments.

We would like to specially acknowledge numerous contributions by Dennis Ferguson (ANS).

2. Introduction

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 [1] and EGP usage in the NSFNET Backbone as described in RFC 1092 [2] and RFC 1093 [3].

The primary function of a BGP speaking system is to exchange network reachability information with other BGP systems. This network reachability information includes information on the list of Autonomous Systems (ASs) that reachability information traverses. This information is sufficient to construct a graph of AS connectivity from which routing loops may be pruned and some policy decisions at the AS level may be enforced.

BGP-4 provides a new set of mechanisms for supporting classless interdomain routing. These mechanisms include support for advertising an IP p...

Processing...
Loading...