%% You should probably cite draft-ietf-dots-signal-filter-control instead of this I-D.
@techreport{nishizuka-dots-signal-control-filtering-01,
    number =    {draft-nishizuka-dots-signal-control-filtering-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-nishizuka-dots-signal-control-filtering/01/},
    author =    {Kaname Nishizuka and Takahiko Nagata and Tirumaleswar Reddy.K and Mohamed Boucadair},
    title =     {{Controlling Filtering Rules Using DOTS Signal Channel}},
    pagetotal = 15,
    year =      2018,
    month =     nov,
    day =       23,
    abstract =  {This document specifies an extension to the DOTS signal channel to control the filtering rules when an attack mitigation is active. Particularly, this extension allows a DOTS client to activate or de- activate filtering rules during a DDoS attack. The characterization of these filtering rules is supposed to be conveyed by a DOTS client during peace time by means of DOTS data channel. Editorial Note (To be removed by RFC Editor) Please update these statements within the document with the RFC number to be assigned to this document: o "This version of this YANG module is part of RFC XXXX;" o "RFC XXXX: Controlling Filtering Rules Using DOTS Signal Channel"; o reference: RFC XXXX o {[}RFCXXXX{]} Please update these statements with the RFC number to be assigned to the following documents: o "RFC SSSS: Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification" (used to be {[}I-D.ietf-dots-signal-channel{]}) o "RFC DDDD: Distributed Denial-of-Service Open Threat Signaling (DOTS) Data Channel Specification" (used to be {[}I-D.ietf-dots-data-channel{]}) Please update the "revision" date of the YANG module.},
}