RPKI Repository Analysis and Requirements
draft-tbruijnzeels-sidr-repo-analysis-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Tim Bruijnzeels , Oleg Muravskiy , Bryan Weber | ||
| Last updated | 2013-08-15 (Latest revision 2013-02-11) | ||
| 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
The current RPKI Resource Certificate Repository Structure (RFC6480 & RFC6481) uses rsync as both a delta and transfer protocol. Concerns have been raised about the scalability of this repository and the reliance on rsync. This document provides an analysis of these concerns and formulates requirements for future work.
Authors
Tim Bruijnzeels
Oleg Muravskiy
Bryan Weber
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)