<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.nro-sidrops-ta-constraints" target="https://datatracker.ietf.org/doc/html/draft-nro-sidrops-ta-constraints-00">
   <front>
      <title>RPKI Trust Anchor Constraints</title>
      <author initials="T." surname="Harrison" fullname="Tom Harrison">
         <organization>APNIC</organization>
      </author>
      <author initials="T." surname="Bruijnzeels" fullname="Tim Bruijnzeels">
         <organization>RIPE NCC</organization>
      </author>
      <author initials="C." surname="Martinez-Cagnazzo" fullname="Carlos Martinez-Cagnazzo">
         <organization>LACNIC</organization>
      </author>
      <author initials="M." surname="Kosters" fullname="Mark Kosters">
         <organization>ARIN</organization>
      </author>
      <author initials="Y." surname="Chadee" fullname="Yogesh Chadee">
         <organization>AFRINIC</organization>
      </author>
      <date month="October" day="20" year="2025" />
      <abstract>
	 <t>   Resource Public Key Infrastructure (RPKI) Relying Parties (RPs) are
   commonly configured with five Trust Anchors (TAs), one for each of
   the Regional Internet Registries (RIRs).  Each TA operator is able to
   make arbitrary RPKI statements about resources independently of the
   other TA operators: for example, one TA could issue a Route Origin
   Authorization (ROA) for resources that have actually been assigned to
   another TA.

   This document specifies a protocol that allows a set of TAs to make
   signed statements that assert their consensus as to the resources for
   which each TA is authoritative.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-nro-sidrops-ta-constraints-00" />
   
</reference>
