Loop detection for imported routes
draft-yue-lsr-loop-detection-for-imported-routes-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Zhuo Yue , Guoqi Xu , Chenxi Li , HaiChao Li | ||
| Last updated | 2023-03-27 (Latest revision 2022-09-23) | ||
| 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
Mutual route import between two IGP instances is often involved in networking solutions. However, routing loops may occur when route are imported to an instance from another and cause critical problem. This document provides a way to detect routing loop and introduces new sub-TLVs to support advertisement IPv4 and IPv6 prefix extended attribute flags and the source router ID of the router which import the route and redistribute the route.
Authors
Zhuo Yue
Guoqi Xu
Chenxi Li
HaiChao Li
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)