BGP Maximum Prefix Limits Inbound
draft-sas-idr-maxprefix-inbound-03
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Melchior Aelmans , Massimiliano Stucchi , Job Snijders | ||
| Last updated | 2021-12-18 (Latest revision 2021-06-16) | ||
| Replaces | draft-sa-idr-maxprefix | ||
| 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
This document describes mechanisms to limit the negative impact of route leaks [RFC7908] and/or resource exhaustion in BGP [RFC4271] implementations.
Authors
Melchior Aelmans
Massimiliano Stucchi
Job Snijders
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)