Prefix Limit Based ORF for BGP-4
draft-keyur-idr-bgp-prefix-limit-orf-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Marco Marzetti , Keyur Patel , John Scudder , Jakob Heitz , Job Snijders | ||
| Last updated | 2018-11-05 (Latest revision 2018-04-26) | ||
| RFC stream | (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
The BGP specification allows for "the ability to impose an (locally configured) upper bound on the number of address prefixes the speaker is willing to accept from a neighbor". In this specification, we define a new Outbound Route Filter type for BGP, termed "Prefix Limit Outbound Route Filter", which the speaker can use to communicate that upper bound to its peer. The peer is then required to abide by the limit. This is expected to have benefits in terms of resource consumption and more importantly, transparency of operation.
Authors
Marco Marzetti
Keyur Patel
John Scudder
Jakob Heitz
Job Snijders
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)