%% You should probably cite draft-ietf-sidrops-signed-tal-15 instead of this revision.
@techreport{ietf-sidrops-signed-tal-03,
    number =    {draft-ietf-sidrops-signed-tal-03},
    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/03/},
    author =    {Tim Bruijnzeels and Carlos M. Martínez and Rob Austein},
    title =     {{RPKI Signed Object for Trust Anchor Keys}},
    pagetotal = 15,
    year =      ** No value found for 'doc.pub_date.year' **,
    month =     ** No value found for 'doc.pub_date' **,
    day =       ** No value found for 'doc.pub_date.day' **,
    abstract =  {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.},
}