Requirement for the transparency of RPKI
draft-qingyuan-transparencyrpki-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Yaping Liu , Shuo Zhang , Qingyuan Li , Sufang Peng | ||
| Last updated | 2020-05-08 (Latest revision 2019-11-05) | ||
| 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 provides the transparency requirement of a Certificate Authority (CA) or Repository resource management agency in Resource Public Key Infrastructure (RPKI), which references multiple content in some RFCs related to RPKI. It is easier for implementers to be aware of these requirements
Authors
Yaping Liu
Shuo Zhang
Qingyuan Li
Sufang Peng
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)