DOI: 10.1007/978-3-540-75476-3_73
|View full text |Cite
|
Sign up to set email alerts
|

High Performance Session State Management Scheme for Stateful Packet Inspection

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2

Citation Types

0
4
0

Publication Types

Select...
4
1

Relationship

0
5

Authors

Journals

citations
Cited by 5 publications
(4 citation statements)
references
References 2 publications
0
4
0
Order By: Relevance
“…SPI is designed to prevent harmful or unsolicited packets entering the computer. SPI was originally developed for firewalls, but so far it has become an important factor in network-based intrusion detection systems (NIDS) and many other applications [ 3 ].…”
Section: Background and Related Workmentioning
confidence: 99%
“…SPI is designed to prevent harmful or unsolicited packets entering the computer. SPI was originally developed for firewalls, but so far it has become an important factor in network-based intrusion detection systems (NIDS) and many other applications [ 3 ].…”
Section: Background and Related Workmentioning
confidence: 99%
“…Flow look-up can be achieved mostly by three ways: Hashing, Bloom Filter (BF) and Tenary Content-Addressable Memory (TCAM). To reduce flow table size, [4] and [8] use a hash of the "raw" flow ID and a hash bucket for hash-collision. The use of a hashed flow ID could result in a dramatically smaller entry size, but the (many-to-one) hash function may cause collisions.…”
Section: Related Workmentioning
confidence: 99%
“…Traditionally, flow tables have been implemented in DRAM [4], [5] and flow look-up is achieved by a tree-based search, hashing and Bloom filters techniques [6] [5], [7]. For highspeed line cards in the routers, implementation of the flow table using a fast but small SRAM for the flow table has been recently proposed in [1], [8]. These approaches hash the flow ID drawn directly from the packets to the address bus of the SRAM, which stores the flow state information.…”
Section: Introductionmentioning
confidence: 99%
“…A large number of short-lived flows or abnormal flows results in significant consumption of the flow memory as well as an increase in the volume of data exchanged for collaboration. Even though a SRAM implementation of the flow table has become typical for fast operations despite its limited capacity [5], [6], this has worsen the scaling problem. Since prediction of the "proper" size of flow table is not trivial, the per-flow monitoring should adapt to the dynamic traffic conditions.…”
Section: Introductionmentioning
confidence: 99%