<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-sidrops-signed-tal" target="https://datatracker.ietf.org/doc/html/draft-ietf-sidrops-signed-tal-02">
   <front>
      <title>RPKI Signed Object for Trust Anchor Keys</title>
      <author initials="T." surname="Bruijnzeels" fullname="Tim Bruijnzeels">
         <organization>NLnet Labs</organization>
      </author>
      <author initials="C." surname="Martinez-Cagnazzo" fullname="Carlos Martinez-Cagnazzo">
         <organization>LACNIC</organization>
      </author>
      <author initials="R." surname="Austein" fullname="Rob Austein">
         <organization>Dragon Research Labs</organization>
      </author>
      <date month="October" day="19" year="2018" />
      <abstract>
	 <t>   Trust Anchor Locators (TALs) [I-D.ietf-sidrops-https-tal] are used by
   Relying Parties in the RPKI to locate and validate Trust Anchor
   certificates used in RPKI validation.  This document defines an RPKI
   signed object for Trust Anchor Keys (TAK), that can be used by Trust
   Anchors to signal their set of current keys and the location(s) of
   the accompanying CA certiifcates to Relying Parties, as well as
   changes to this set in the form of revoked keys and new keys, in
   order to support both planned and unplanned key rolls without
   impacting RPKI validation.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-sidrops-signed-tal-02" />
   
</reference>
