Operational Experience with the BGP-4 protocol
draft-ietf-idr-bgp4-op-experience-02
| Document | Type |
Expired Internet-Draft
(idr WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Paul S. Traina | ||
| Last updated | 2024-08-23 (Latest revision 1996-05-14) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Dead WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The purpose of this memo is to document how the requirements for advancing a routing protocol to Full Standard have been satisfied by Border Gateway Protocol version 4 (BGP-4). This report documents experience with BGP. It is the second of two reports on the BGP protocol. The remaining sections of this memo document how BGP satisfies General Requirements specified in Section 3.0, as well as the Requirements for Full Standard as specified in Section 6.0 of the 'Internet Routing Protocol Standardization Criteria' document [1]. Please send comments to bgp@ans.net.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)