Skip to main content

IS-IS Extensions for Flow Specification
draft-you-isis-flowspec-extensions-04

Document Type Expired Internet-Draft (candidate for isis WG)
Expired & archived
Authors Jianjie You , liangqiandeng , Keyur Patel , Peng Fan , Zhenqiang Li
Last updated 2016-08-17 (Latest revision 2016-02-14)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Additional resources Mailing list discussion
Stream WG state Call For Adoption By WG Issued
Polled for WG adoption but not adopted
Document shepherd (None)
IESG IESG state Expired
Consensus boilerplate Unknown
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 rules are used to distribute traffic filtering rules that are used to filter Denial-of-Service (DoS) attacks. For the networks that only deploy IS-IS or IS-IS variant, it is required that IS-IS is extended to distribute Flow Specification or FlowSpec rules. This document discusses the use cases for distributing flow specification (FlowSpec) routes using IS-IS. Furthermore, this document defines a new IS-IS FlowSpec Reachability TLV encoding format that can be used to distribute FlowSpec rules, its validation procedures for imposing the filtering information on the routers, and a capability to indicate the support of FlowSpec functionality.

Authors

Jianjie You
liangqiandeng
Keyur Patel
Peng Fan
Zhenqiang Li

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