%% You should probably cite rfc5452 instead of this I-D.
@techreport{ietf-dnsext-forgery-resilience-10,
    number =    {draft-ietf-dnsext-forgery-resilience-10},
    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-dnsext-forgery-resilience/10/},
    author =    {Bert Hubert and Remco Mook},
    title =     {{Measures for Making DNS More Resilient against Forged Answers}},
    pagetotal = 18,
    year =      2008,
    month =     dec,
    day =       15,
    abstract =  {The current Internet climate poses serious threats to the Domain Name System. In the interim period before the DNS protocol can be secured more fully, measures can already be taken to harden the DNS to make 'spoofing' a recursing nameserver many orders of magnitude harder. Even a cryptographically secured DNS benefits from having the ability to discard bogus responses quickly, as this potentially saves large amounts of computation. By describing certain behavior that has previously not been standardized, this document sets out how to make the DNS more resilient against accepting incorrect responses. This document updates RFC 2181. {[}STANDARDS-TRACK{]}},
}