%% You should probably cite draft-sriram-replay-protection-design-discussion-13 instead of this revision.
@techreport{sriram-replay-protection-design-discussion-03,
    number =    {draft-sriram-replay-protection-design-discussion-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-sriram-replay-protection-design-discussion/03/},
    author =    {Kotikalapudi Sriram and Doug Montgomery},
    title =     {{Design Discussion and Comparison of Replay-Attack Protection Mechanisms for BGPSEC}},
    pagetotal = 16,
    year =      2014,
    month =     mar,
    day =       26,
    abstract =  {The BGPSEC protocol requires a method for protection from replay attacks, at least to control the window of exposure. In the context of BGPSEC, a replay attack occurs when an adversary suppresses a prefix withdrawal (implicit or explicit) or replays a previously received BGPSEC announcement for a prefix that has since been withdrawn. This informational document provides design discussion and comparison of multiple alternative replay-attack protection mechanisms weighing their pros and cons. It is meant to be a companion document to the standards track I-D.-ietf-sidr-bgpsec- rollover that will specify a method to be used with BGPSEC for replay-attack protection.},
}