%% You should probably cite draft-ietf-sidrops-signed-tal-14 instead of this revision. @techreport{ietf-sidrops-signed-tal-06, number = {draft-ietf-sidrops-signed-tal-06}, 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-signed-tal/06/}, author = {Carlos M. Martínez and George G. Michaelson and Tom Harrison and Tim Bruijnzeels and Rob Austein}, title = {{RPKI Signed Object for Trust Anchor Keys}}, pagetotal = 18, year = 2020, month = nov, day = 2, abstract = {A Trust Anchor Locator (TAL) {[}I-D.ietf-sidrops-https-tal{]} is used by Relying Parties (RP) in the RPKI to locate and validate a Trust Anchor (TA) CA certificate used in RPKI validation. This document defines an RPKI signed object for a set of Trust Anchor Keys (TAK), that can be used by TA creators and publishers to signal their set of current keys and the location(s) of the accompanying CA certificates to RPs, 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.}, }