BGP Maximum Prefix Limits
draft-sa-grow-maxprefix-02
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2019-09-09 (latest revision 2019-03-08) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-sa-grow-maxprefix-02.txt
https://www.ietf.org/archive/id/draft-sa-grow-maxprefix-02.txt
Abstract
This document describes mechanisms to limit the negative impact of route leaks [RFC7908] and/or resource exhaustion in BGP [RFC4271] implementations.
Authors
Job Snijders
(job@ntt.net)
Melchior Aelmans
(maelmans@juniper.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)