%% You should probably cite draft-ietf-ospf-flowspec-extensions instead of this I-D.
@techreport{liang-ospf-flowspec-extensions-04,
	number =	{draft-liang-ospf-flowspec-extensions-04},
	type =		{Internet-Draft},
	institution =	{Internet Engineering Task Force},
	publisher =	{Internet Engineering Task Force},
	note =		{Work in Progress},
	url =		{https://datatracker.ietf.org/doc/html/draft-liang-ospf-flowspec-extensions-04},
        author =	{Qiandeng Liang and Jianjie You and Nan Wu and Peng Fan and Keyur Patel},
	title =		{{OSPF Extensions for Flow Specification}},
	pagetotal =	18,
	year =		,
	month =		,
	day =		,
	abstract =	{Dissemination of the Traffic flow information was first introduced in the BGP protocol {[}RFC5575{]}. FlowSpec routes are used to distribute traffic filtering rules that are used to filter the Denial-of-Service (DoS) attacks. For the networks that only deploy IGP (Interior Gateway Protocol) (e.g. OSPF), it is expected to extend the IGP to distribute Flow Specification or FlowSpec routes. This document discusses the use cases for distributing flow specification (FlowSpec) routes using OSPF. Furthermore, this document defines a new OSPF FlowSpec Opaque Link State Advertisement (LSA) encoding format that can be used to distribute FlowSpec routes, its validation procedures for imposing the filtering information on the routers and a capability to indicate the support of FlowSpec functionality.},
}