Design Discussion of Route Leaks Solution Methods
draft-sriram-idr-route-leak-solution-discussion-01
The information below is for an old version of the document.
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
---|---|---|---|
Author | Kotikalapudi Sriram | ||
Last updated | 2019-08-04 (Latest revision 2019-01-31) | ||
RFC stream | (None) | ||
Formats | |||
Additional resources | |||
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
This document captures the design rationale of the route leaks solution document [draft-ietf-idr-route-leak-detection-mitigation]. The designers needed to balance many competing factors, and this document provides insights into the design questions and their resolution.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)