Skip to main content

Problem Statement and Considerations for ROAs issued with Multiple Prefixes
draft-yan-sidrops-roa-considerations-06

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Zhiwei Yan , Randy Bush , Guanggang Geng , Jiankang Yao
Last updated 2021-09-26 (Latest revision 2021-03-25)
Replaced by draft-ietf-sidrops-roa-considerations
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-sidrops-roa-considerations
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

The address space holder needs to issue an ROA object when it authorizes one or more ASes to originate routes to multiple prefixes. During the process of ROA issuance, the address space holder needs to specify an origin AS for a list of IP prefixes. Besides, the address space holder has a free choice to put multiple prefixes into a single ROA or issue separate ROAs for each prefix based on the current specification. This memo analyzes and presents some operational problems which may be caused by the misconfigurations of ROAs containing multiple IP prefixes. Some suggestions and considerations also have been proposed.

Authors

Zhiwei Yan
Randy Bush
Guanggang Geng
Jiankang Yao

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