Skip to main content

Issue in Route Origin Validation from Route Partial Visibility
draft-wang-sidrops-route-partial-visibility-01

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Shuhe Wang , Ke Xu , Qi Li , Zhuotao Liu
Last updated 2026-06-08 (Latest revision 2025-12-05)
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

In the Resource Public Key Infrastructure (RPKI), validating prefix- origin pairs using Route Origin Authorizations (ROAs) globally and performing Route Origin Validation (ROV) locally at each Autonomous System (AS) with validated ROA payloads (VRPs) can lead to inconsistent results due to partial route visibility. This document highlights how partial route visibility can turn originally non-loose ROAs into loose VRPs, outlines the causes of partial route visibility, and discusses potential solutions to mitigate the issue.

Authors

Shuhe Wang
Ke Xu
Qi Li
Zhuotao Liu

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)