%% You should probably cite draft-ietf-sidrops-avoid-rpki-state-in-bgp instead of this I-D.
@techreport{spaghetti-sidrops-avoid-rpki-state-in-bgp-01,
    number =    {draft-spaghetti-sidrops-avoid-rpki-state-in-bgp-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-spaghetti-sidrops-avoid-rpki-state-in-bgp/01/},
    author =    {Job Snijders and Tobias Fiebig and Massimiliano Stucchi},
    title =     {{Guidance to Avoid Carrying RPKI Validation States in Transitive BGP Path Attributes}},
    pagetotal = 13,
    year =      2024,
    month =     feb,
    day =       23,
    abstract =  {This document provides guidance to avoid carrying Resource Public Key Infrastructure (RPKI) derived Validation States in Transitive Border Gateway Protocol (BGP) Path Attributes. Annotating routes with attributes signaling validation state may flood needless BGP UPDATE messages through the global Internet routing system, when, for example, Route Origin Authorizations are issued, revoked, or RPKI-To- Router sessions are terminated. Operators SHOULD ensure Validation States are not signalled in transitive BGP Path Attributes. Specifically, Operators SHOULD NOT group BGP routes by their Prefix Origin Validation state into distinct BGP Communities.},
}