Relax the AS Loop Detection for Aggregates in BGP
draft-chen-idr-asloop-aggr-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Enke Chen , Stefan Olofsson | ||
| Last updated | 2022-04-21 (Latest revision 2021-10-18) | ||
| RFC stream | (None) | ||
| Intended RFC status | (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
Currently an BGP aggregate may be denied or excluded by the AS loop detection mechanism when a more specific, contributing route contains the local AS number. To help enhance network robustness and simplify network operations, in this document we propose that the AS loop detection be relaxed for aggregates with an AS_SET path segment.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)