RPKI Certificate Tree Validation by the RIPE NCC RPKI Validator
draft-ietf-sidrops-rpki-tree-validation-01
| Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 8488.
Expired & archived
|
|
|---|---|---|---|
| Authors | Oleg Muravskiy , Tim Bruijnzeels | ||
| Last updated | 2018-04-19 (Latest revision 2017-07-20) | ||
| Replaces | draft-ietf-sidr-rpki-tree-validation | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Reviews | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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 the approach to validate the content of the RPKI certificate tree, as it is implemented in the RIPE NCC RPKI Validator. This approach is independent of a particular object retrieval mechanism. This allows it to be used with repositories available over the rsync protocol, the RPKI Repository Delta Protocol, and repositories that use a mix of both.
Authors
Oleg Muravskiy
Tim Bruijnzeels
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)