%% You should probably cite rfc8198 instead of this I-D.
@techreport{ietf-dnsop-nsec-aggressiveuse-00,
    number =    {draft-ietf-dnsop-nsec-aggressiveuse-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-dnsop-nsec-aggressiveuse/00/},
    author =    {Kazunori Fujiwara and Akira Kato and Warren "Ace" Kumari},
    title =     {{Aggressive use of NSEC/NSEC3}},
    pagetotal = 16,
    year =      2016,
    month =     jun,
    day =       27,
    abstract =  {The DNS relies upon caching to scale; however, the cache lookup generally requires an exact match. This document specifies the use of NSEC/NSEC3 resource records to generate negative answers within a range. This increases resilience to DoS attacks, increases performance / decreases latency, decreases resource utilization on both authoritative and recursive servers, and also increases privacy. This document updates RFC4035 by allowing resolvers to generate negative answers based upon NSEC/NSEC3 records. {[} Ed note: Text inside square brackets ({[}{]}) is additional background information, answers to frequently asked questions, general musings, etc. They will be removed before publication.This document is being collaborated on in Github at: https://github.com/wkumari/draft-ietf- dnsop-nsec-aggressiveuse. The most recent version of the document, open issues, etc should all be available here. The authors (gratefully) accept pull requests. Known / open issues {[}To be moved to Github issue tracker{]}:},
}