RPKI-Based Policy Without Route Refresh
draft-ymbk-sidrops-rov-no-rr-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Randy Bush , Keyur Patel , Dr. Philip F. Smith , Mark Tinka | ||
| Last updated | 2022-05-19 (Latest revision 2021-11-15) | ||
| 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
A BGP Speaker performing RPKI-based policy should not issue Route Refresh to its neighbors when receiving new RPKI data. A method for avoiding doing so is described.
Authors
Randy Bush
Keyur Patel
Dr. Philip F. Smith
Mark Tinka
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)