Problem Statement and Considerations for ROA containing Multiple Prefixes
draft-ietf-sidrops-roa-considerations-01
| Document | Type | Expired Internet-Draft (sidrops WG) | |
|---|---|---|---|
| Authors | Zhiwei Yan , Randy Bush , Guanggang Geng , Jiankang Yao | ||
| Last updated | 2022-04-29 (Latest revision 2021-10-26) | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | Keyur Patel | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | keyur@arrcus.com |
https://www.ietf.org/archive/id/draft-ietf-sidrops-roa-considerations-01.txt
Abstract
The address space holder needs to issue an ROA object when it authorizes one or more ASes to originate routes to IP prefix(es). During the process of ROA issuance, the address space holder may need 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 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.)