Multi Instance BGP
draft-raszuk-mi-bgp-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Robert Raszuk | ||
| Last updated | 2019-04-25 (Latest revision 2018-10-22) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
As the number of operational use cases of BGP grows there is demand to increase the level of separation and processing independence between various address families carried by BGP today. This document augments base BGP specification in allowing local configuration of BGP port number by the operator to run parallel fully disjoined BGP instances allowing full processing separation between them. While local BGP implementation may already assure BGP process or thread robustnes the general aim here is to allow similar level of groups of BGP address families independence when running BGP code on general purpose hardware as well as x86 based route reflectors.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)