OSPF Extensions for Flow Specification
draft-liang-lsr-ospf-flowspec-extensions-01
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | liangqiandeng , Qiangzhou Gao , Hang Shi , Keyur Patel , Acee Lindem | ||
Last updated | 2023-11-06 (Latest revision 2023-04-24) | ||
Replaces | draft-ietf-ospf-flowspec-extensions | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Dissemination of the Traffic flow information was first introduced in the BGP protocol [RFC5575]. FlowSpec routes are used to distribute traffic filtering rules used to filter Denial-of-Service (DoS) attacks. For 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 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
Qiangzhou Gao
Hang Shi
Keyur Patel
Acee Lindem
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)