Difference between revisions of "Project Proposals/uDPI"

From fd.io
Jump to: navigation, search
(Initial Committers)
(Description)
Line 28: Line 28:
 
== Description ==
 
== Description ==
 
<!-- Description of the work that will take place in this project -->
 
<!-- Description of the work that will take place in this project -->
uDPI (Universal Deep Packet Inspection) is a reference framework to provide a high performance solution for Deep Packet Inspection. It leverages industry regex matching library to provide rich features, which can be used in IPS/IDS, Web Firewall, etc.
+
The uDPI (Universal Deep Packet Inspection) project is a reference framework to build a high performance solution for Deep Packet Inspection, integrated with the general purpose FD.io VPP stack. It leverages industry regex matching library to provide a rich set of features, which can be used in IPS/IDS, Web Firewall and similar applications.  
  
We are planning to contribute existing code, and initial code is contributed by Intel and Travelping.
+
The initial code contributions are from Intel and Travelping.
  
Below are the uDPI reference framework:
+
Overview of the uDPI reference framework:  
[[File:Reference.png|thumb|uDPI Reference Framework]]
+
https://wiki.fd.io/view/File:Reference.png
  
 
== Scope ==
 
== Scope ==

Revision as of 01:53, 25 July 2019


Name

uDPI

Project Contact Name and Email

Repository Name

udpi

Description

The uDPI (Universal Deep Packet Inspection) project is a reference framework to build a high performance solution for Deep Packet Inspection, integrated with the general purpose FD.io VPP stack. It leverages industry regex matching library to provide a rich set of features, which can be used in IPS/IDS, Web Firewall and similar applications.

The initial code contributions are from Intel and Travelping.

Overview of the uDPI reference framework: https://wiki.fd.io/view/File:Reference.png

Scope

uDPI's main responsibility is to provide a reference framework for Deep Packet Inspection. It will cover below key components:

  • Flow Classification
    • HW flow offloading leveraging rte_flow on DPDK
    • SW flow classification
    • Supports both ipv4 and ipv6 flows
    • Supports Tunnel Traffic Classification
    • BD-aware and VRF-aware
    • Bi-directional traffic maps to one flow.
  • Flow Expiration
    • Timer-based expiration mechanism
    • TCP session aware expiration mechanism
  • TCP Segments Reassembly
    • TCP connection track
    • TCP segments re-ordering
    • TCP segments overlap handling
  • Application Database
    • Default static Application Database
    • Add new Application rules dynamically
  • Application Detection
    • Leverage Hyperscan Stream Mode
    • Reassembly TCP segments on the fly
  • Application-based Actions
    • Qos
    • Rate Limiting
    • Policy Routing
    • SDWAN
  • Supported Protocols:
    • TLS/HTTPS
    • HTTP
    • DNS
    • QUIC

......

Initial Committers

Vendor Neutral

No current or expected issues with vendor neutrality.

Meets Board Policy (including IPR, being within Board defined Scope etc)

Meets board policy as expressed in Technical Community Charter and IP Policy

Administrata

  • Request for Project proposal consideration
    • Email: (place link to email to TSC proposing project, this can be obtained from TSC Archives
    • Date: (date proposed, makes it simpler to calculate the pre-requisite 2 week time period of gestation before being permitted to be voted on)