The Use of Maxlength in the RPKI
draft-yossigi-rpkimaxlen-02
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Yossi Gilad , Sharon Goldberg , Kotikalapudi Sriram , Job Snijders , Ben Maddison | ||
| Last updated | 2018-03-05 | ||
| Replaced by | RFC 9319 | ||
| 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-rpkimaxlen | |
| 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 recommends that operators avoid using the maxLength attribute when issuing Route Origin Authorizations (ROAs) in the Resource Public Key Infrastructure (RPKI). These recommendations complement those in [RFC7115].
Authors
Yossi Gilad
Sharon Goldberg
Kotikalapudi Sriram
Job Snijders
Ben Maddison
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)