Inbound BGP Maximum Prefix Limits
draft-sas-idr-maxprefix-inbound-05
| Document | Type |
Expired Internet-Draft
(candidate for idr WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Job Snijders , Melchior Aelmans , Massimiliano Stucchi | ||
| Last updated | 2023-08-08 (Latest revision 2023-02-04) | ||
| Replaces | draft-sa-idr-maxprefix | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Call For Adoption By WG Issued | |
| Document shepherd | Susan Hares | ||
| Shepherd write-up | Show Last changed 2023-03-28 | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | shares@ndzh.com |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes two threshold types to consider when receiving BGP address prefixes from adjacent systems in order to limit the negative impact of route leaks or resource exhaustion in BGP implementations.
Authors
Job Snijders
Melchior Aelmans
Massimiliano Stucchi
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)