BGP Maximum Prefix Limits
draft-sa-grow-maxprefix-02
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Job Snijders , Melchior Aelmans | ||
| Last updated | 2019-09-09 (Latest revision 2019-03-08) | ||
| Replaced by | draft-sa-idr-maxprefix | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-sa-idr-maxprefix | |
| 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
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)