OSPF Extensions for Flow Specification
draft-ietf-ospf-flowspec-extensions-01

Document Type Expired Internet-Draft (ospf WG)
Last updated 2016-10-16 (latest revision 2016-04-14)
Replaces draft-liang-ospf-flowspec-extensions
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state WG Document (wg milestone: Jun 2017 - Standardize OSPF Flo... )
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-ospf-flowspec-extensions-01.txt

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 Denial-of-Service (DoS) attacks. For the networks that only deploy an IGP (Interior Gateway Protocol) (e.g., OSPF), it is required that the IGP is extended 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 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.

Authors

liangqiandeng (liangqiandeng@huawei.com)
Jianjie You (youjianjie@huawei.com)
Nan Wu (eric.wu@huawei.com)
Peng Fan (peng.fan@139.com)
Keyur Patel (keyupate@cisco.com)
Acee Lindem (acee@cisco.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)