The Use of Maxlength in the RPKI
draft-yossigi-rpkimaxlen-02

Document Type Replaced Internet-Draft (individual)
Last updated 2018-03-05
Replaced by draft-ietf-sidrops-rpkimaxlen
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-sidrops-rpkimaxlen
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-yossigi-rpkimaxlen-02.txt

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 (yossigi@bu.edu)
Sharon Goldberg (goldbe@cs.bu.edu)
Kotikalapudi Sriram (kotikalapudi.sriram@nist.gov)
Job Snijders (job@ntt.net)
Ben Maddison (benm@workonline.co.za)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)