%% You should probably cite draft-ietf-sidrops-manifest-numbers-05 instead of this revision.
@techreport{ietf-sidrops-manifest-numbers-00,
    number =    {draft-ietf-sidrops-manifest-numbers-00},
    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-manifest-numbers/00/},
    author =    {Tom Harrison and George Michaelson and Job Snijders},
    title =     {{RPKI Manifest Number Handling}},
    pagetotal = 10,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {The Resource Public Key Infrastructure (RPKI) makes use of signed objects called manifests. A manifest lists each file that a publisher intends to include within an RPKI repository, and can be used to detect certain forms of attack against a repository. Manifests include a "manifest number" (manifestNumber), which the publisher must increment whenever it issues a new manifest, and Relying Parties (RPs) are required to verify that a newly-retrieved manifest for a given Certification Authority (CA) has a higher manifestNumber than the previously-validated manifest. However, the manifestNumber field is 20 octets in length (i.e. not unbounded), and no behaviour is specified for when a manifestNumber reaches the largest possible value. This document specifies publisher and RP behaviour for this scenario.},
}