%% You should probably cite rfc8630 instead of this I-D. @techreport{ietf-sidrops-https-tal-07, number = {draft-ietf-sidrops-https-tal-07}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-sidrops-https-tal/07/}, author = {Geoff Huston and Samuel Weiler and George G. Michaelson and Stephen Kent and Tim Bruijnzeels}, title = {{Resource Public Key Infrastructure (RPKI) Trust Anchor Locator}}, pagetotal = 11, year = 2019, month = mar, day = 4, abstract = {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.}, }