<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-sidrops-rpkimaxlen" target="https://datatracker.ietf.org/doc/html/draft-ietf-sidrops-rpkimaxlen-00">
   <front>
      <title>The Use of Maxlength in the RPKI</title>
      <author initials="Y." surname="Gilad" fullname="Yossi Gilad">
         <organization>Boston University</organization>
      </author>
      <author initials="S." surname="Goldberg" fullname="Sharon Goldberg">
         <organization>Boston University</organization>
      </author>
      <author initials="K." surname="Sriram" fullname="Kotikalapudi Sriram">
         <organization>USA National Institute of Standards and Technology</organization>
      </author>
      <author initials="J." surname="Snijders" fullname="Job Snijders">
         <organization>NTT Communications</organization>
      </author>
      <author initials="B." surname="Maddison" fullname="Ben Maddison">
         <organization>Workonline Communications</organization>
      </author>
      <date month="May" day="1" year="2018" />
      <abstract>
	 <t>   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].

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-sidrops-rpkimaxlen-00" />
   
</reference>
