Route Origin Authorization (ROA) Governance for Anycasted Services with Unique Origin ASNs
draft-pbs-sidrops-roaanycast-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | L. Poulopoulos , S. Boudjema , hasan siddique | ||
| Last updated | 2026-03-16 (Latest revision 2025-09-03) | ||
| 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
This document describes a set of best practices for the management of Route Origin Authorizations (ROAs) used to certify globally anycasted services with unique origin autonomous system numbers (ASNs) per node. It identifies key risk areas related to anycast-based ROA publication and how to mitigate technical risk for RPKI operations.
Authors
L. Poulopoulos
S. Boudjema
hasan siddique
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)