<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-sidrops-https-tal" target="https://datatracker.ietf.org/doc/html/draft-ietf-sidrops-https-tal-06">
   <front>
      <title>Resource Public Key Infrastructure (RPKI) Trust Anchor Locator</title>
      <author initials="G." surname="Huston" fullname="Geoff Huston">
         <organization>APNIC</organization>
      </author>
      <author initials="S." surname="Weiler" fullname="Sam Weiler">
         <organization>W3C/MIT</organization>
      </author>
      <author initials="G." surname="Michaelson" fullname="George Michaelson">
         <organization>APNIC</organization>
      </author>
      <author initials="S." surname="Kent" fullname="Stephen Kent">
         <organization>Unaffiliated</organization>
      </author>
      <author initials="T." surname="Bruijnzeels" fullname="Tim Bruijnzeels">
         <organization>NLnet Labs</organization>
      </author>
      <date month="January" day="23" year="2019" />
      <abstract>
	 <t>   This document defines a Trust Anchor Locator (TAL) for the Resource
   Public Key Infrastructure (RPKI).  TALs allow Relying Parties in the
   RPKI to download the current Trust Anchor (TA) CA certificate from
   one or more locations, and verify that the key of this self-signed
   certificate matches the key on the TAL.  Thus, Relying Parties can be
   configured with TA keys, but allow these TAs to change the content of
   their CA certificate.  In particular it allows TAs to change the set
   of Internet Number Resources included in the RFC3779 extension of
   their certificate.

   This document obsoletes the previous definition of Trust Anchor
   Locators in RFC 7730 by adding support for HTTPS URIs.

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