%% You should probably cite draft-ietf-dkim-replay-problem instead of this I-D.
@techreport{chuang-dkim-replay-problem-00,
    number =    {draft-chuang-dkim-replay-problem-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-chuang-dkim-replay-problem/00/},
    author =    {Wei Chuang and Allen Robin and Bron Gondwana},
    title =     {{DKIM Replay Problem Statement and Scenarios}},
    pagetotal = 12,
    year =      2022,
    month =     oct,
    day =       21,
    abstract =  {DKIM {[}RFC6376{]} is an IETF standard for the cryptographic protocol to sign and authenticate email at the domain level and protect the integrity of messages during transit. In particular this enables DKIM to be able authenticate email through email forwarding. Section 8.6 of {[}RFC6376{]} defines a vulnerability called DKIM Replay as a spam message sent through a SMTP MTA DKIM signer, that then is sent to many more recipients, leveraging the reputation of the signer. This document defines the damage this causes to email delivery and interoperability, and the impacted mail flows. Part of the reason why this is such a difficult problem is that receivers have a hard time differentiating between legitimate forwarding flows and DKIM replay.},
}