BGP Maximum Prefix Limits Inbound
draft-sas-idr-maxprefix-inbound-04
| 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 | 2022-07-25 (Latest revision 2022-01-19) | ||
| Replaces | draft-sa-idr-maxprefix | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Candidate for WG Adoption | |
| Document shepherd | Susan Hares | ||
| Shepherd write-up | Show Last changed 2022-03-10 | ||
| 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 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.)